From palos at post.sk Mon Dec 1 01:21:24 2008 From: palos at post.sk (Palo S.) Date: 01 Dec 2008 02:21:24 +0100 (CET) Subject: [Ekiga-list] \"remote user cleared the call\" problem Message-ID: <49333C14.000001.01872@kamasutra> The problem disappeared after I disabled forwarding of 5060 to the called machine. So yet another NAT issue. However the port forwarding was set a long time ago and the problem only appeared recently, confirming that the new Ekiga server was the trigger of the problem. It would be nice if Kamailio could handle the network settings that the previous server did but I am not sure whether somebody wants to look at this - if so, then I can provide any information required. Palo __________ http://sport.sme.sk - Najkomplexnej?ie inform?cie zo ?portu From rcook at wyrms.net Mon Dec 1 01:45:26 2008 From: rcook at wyrms.net (Robin Cook) Date: Sun, 30 Nov 2008 19:45:26 -0600 Subject: [Ekiga-list] ptlib failing to build In-Reply-To: <20081130163118.2c94a428@beernabeer.com> References: <20081130163118.2c94a428@beernabeer.com> Message-ID: <1228095926.19582.2.camel@localhost> I am getting the same error but I have libiodbc installed so it must have the same header. CuZnDragon Robin Cook On Sun, 2008-11-30 at 16:31 -0600, George Sherwood wrote: > Recently ptlib 2.4.2 started to fail to build with this error: > > make[1]: Entering directory `/usr/src/ptlib-2.4.2' > make[1]: Leaving directory `/usr/src/ptlib-2.4.2' > set -e; if test -e src ; then /usr/bin/make -C src optshared; fi; if test -e plugins ; then /usr/bin/make -C plugins optshared; fi; > make[1]: Entering directory `/usr/src/ptlib-2.4.2/src' > /usr/bin/make DEBUG= P_SHAREDLIB=1 default_target > make[2]: Entering directory `/usr/src/ptlib-2.4.2/src' > g++ -DPTRACING=1 -D_REENTRANT -fno-exceptions -Wall -fPIC -DPIC -DNDEBUG -I/usr/src/ptlib-2.4.2/include -Os -march=pentium4 -pipe -Os -felide-constructors -Wreorder -c ptclib/pssl.cxx -o /usr/src/ptlib-2.4.2/lib_linux_x86/obj/pssl.o > g++ -DPTRACING=1 -D_REENTRANT -fno-exceptions -Wall -fPIC -DPIC -DNDEBUG -I/usr/src/ptlib-2.4.2/include -Os -march=pentium4 -pipe -Os -felide-constructors -Wreorder -c ptclib/podbc.cxx -o /usr/src/ptlib-2.4.2/lib_linux_x86/obj/podbc.o > make[2]: Leaving directory `/usr/src/ptlib-2.4.2/src' > make[1]: Leaving directory `/usr/src/ptlib-2.4.2/src' > In file included from /usr/src/ptlib-2.4.2/include/ptclib/podbc.h:105, > from ptclib/podbc.cxx:40: > /usr/include/sqlext.h:2111: error: 'BOOL' does not name a type > ptclib/podbc.cxx: In member function 'PBoolean PODBCRecord::IsColumnUpdatable(PINDEX)': > ptclib/podbc.cxx:1534: error: cannot convert 'SWORD*' to 'SQLINTEGER*' for argument '7' to 'SQLRETURN SQLColAttribute(void*, SQLUSMALLINT, SQLUSMALLINT, void*, SQLSMALLINT, SQLSMALLINT*, SQLINTEGER*)' > ptclib/podbc.cxx: In member function 'PBoolean PODBCRecord::IsColumnAutoIndex(PINDEX)': > ptclib/podbc.cxx:1548: error: cannot convert 'SWORD*' to 'SQLINTEGER*' for argument '7' to 'SQLRETURN SQLColAttribute(void*, SQLUSMALLINT, SQLUSMALLINT, void*, SQLSMALLINT, SQLSMALLINT*, SQLINTEGER*)' > ptclib/podbc.cxx: In member function 'unsigned int PODBCRecord::ColumnPrecision(PINDEX)': > ptclib/podbc.cxx:1561: error: cannot convert 'SWORD*' to 'SQLINTEGER*' for argument '7' to 'SQLRETURN SQLColAttribute(void*, SQLUSMALLINT, SQLUSMALLINT, void*, SQLSMALLINT, SQLSMALLINT*, SQLINTEGER*)' > make[2]: *** [/usr/src/ptlib-2.4.2/lib_linux_x86/obj/podbc.o] Error 1 > make[1]: *** [optshared] Error 2 > make: *** [optshared] Error 2 > > > The include /usr/include/sqlext.h:2111 is from unixodbc 2.2.13. I am > fairly sure that I had unixodbc installed before when ptlib was > building fine. It might have been updated since that time. I > removed unixodbc and ptlib built fine. > > Any way to make these co-exist? > > George > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 835 bytes Desc: This is a digitally signed message part URL: From 1986.arun at gmail.com Mon Dec 1 18:48:49 2008 From: 1986.arun at gmail.com (arun sreedhara) Date: Tue, 2 Dec 2008 00:18:49 +0530 Subject: [Ekiga-list] problem in registering user agent Message-ID: <8480dfc30812011048jd15fc8cm9393ff0800a0a2be@mail.gmail.com> hi, I am using sofia-sip stack to develop an user agent,As a first step i thought of writing a simple instant messaging application. For that, am trying to register my sip address to ekiga registrar but am getting service unavailable message from the sofia stack. Here is the code snippet : /*create NUA stack */ appl->nua = nua_create(appl->root,app_callback,appl, SIPTAG_FROM_STR("sip:xxx at ekiga.net"), NUTAG_PROXY("sip:86.64.162.35:5060"), TAG_NULL()); nua_set_params(appl->nua, NUTAG_ENABLEMESSAGE(1), NUTAG_ENABLEINVITE(1), NUTAG_AUTOALERT(1), NUTAG_SESSION_TIMER(0), NUTAG_AUTOANSWER(0), TAG_NULL()); if (appl->nua != NULL) { nua_handle_t *nh; to = sip_to_make(appl->home, "sip:xxx at ekiga.net"); if (to == NULL) { return 0; } nh = nua_handle(appl->nua, NULL,NUTAG_URL(to->a_url),SIPTAG_TO(to),TAG_END()); nua_register(nh, TAG_END()); /* enter main loop for processing of messages */ su_root_run(appl->root); In the call back registered am getting service unavailable message..Can any body help me on this issue?? Thanks in advance !! From dsandras at seconix.com Mon Dec 1 19:31:44 2008 From: dsandras at seconix.com (Damien Sandras) Date: Mon, 01 Dec 2008 20:31:44 +0100 Subject: [Ekiga-list] \"remote user cleared the call\" problem In-Reply-To: <49333C14.000001.01872@kamasutra> References: <49333C14.000001.01872@kamasutra> Message-ID: <1228159904.4359.2.camel@scorpion.multitel.be> Le lundi 01 d?cembre 2008 ? 02:21 +0100, Palo S. a ?crit : > The problem disappeared after I disabled forwarding > of 5060 to the called machine. So yet another NAT > issue. However the port forwarding was set a long > time ago and the problem only appeared recently, > confirming that the new Ekiga server was the trigger > of the problem. It would be nice if Kamailio could > handle the network settings that the previous server > did but I am not sure whether somebody wants to look > at this - if so, then I can provide any information > required. > A cancel can be sent if you are using forking, ie 2 Ekiga registered with the same account name, from 2 different IP addresses and ports. As soon as one answers, a CANCEL is sent to the other one. Couldn't it be the case ? -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From dsandras at seconix.com Mon Dec 1 19:32:10 2008 From: dsandras at seconix.com (Damien Sandras) Date: Mon, 01 Dec 2008 20:32:10 +0100 Subject: [Ekiga-list] [Ekiga-devel-list] Professional use of Ekiga : need someone for an interview In-Reply-To: References: <1225875179.4990.197.camel@scorpion.multitel.be> <1226413684.4428.121.camel@scorpion.multitel.be> Message-ID: <1228159930.4359.4.camel@scorpion.multitel.be> Le dimanche 30 novembre 2008 ? 12:46 -0500, RazaMetaL | Only The Good Die Young a ?crit : > On Tue, Nov 11, 2008 at 9:28 AM, Damien Sandras wrote: > > > > Hello, > > > > Le mercredi 05 novembre 2008 ? 09:52 +0100, Damien Sandras a ?crit : > > > Hello, > > > > > > A journalist from LinuxWorld would like to interview somebody who is > > > using Ekiga professionally in a corporate environment. > > > > > > Is there an enthousiast candidate ? If so, please contact me. > > > > We still need one person using Ekiga for SIP. > > > Hi Damien, > > The article and interviews are at: > > http://www.computerworld.com/action/article.do?command=viewArticleBasic&taxonomyName=Networking+and+Internet&articleId=9120718&taxonomyId=16&pageNumber=2 > > Best regards, > Thank you for the great article and the time you spent on it, it is much appreciated! -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From enp at altlinux.org Mon Dec 1 05:43:12 2008 From: enp at altlinux.org (Eugene Prokopiev) Date: Mon, 1 Dec 2008 08:43:12 +0300 Subject: [Ekiga-list] Network interface for Ekiga 3.0.1 Message-ID: Hi, How can I setup network interface for Ekiga 3.0.1? It was possible with Ekiga 2.0.12 in Edit - Prefernces - Protocol - Network Settings. But now there are no such option :( -- Thanks, Eugene Prokopiev From dsandras at seconix.com Mon Dec 1 21:25:27 2008 From: dsandras at seconix.com (Damien Sandras) Date: Mon, 01 Dec 2008 22:25:27 +0100 Subject: [Ekiga-list] Network interface for Ekiga 3.0.1 In-Reply-To: References: Message-ID: <1228166727.4359.6.camel@scorpion.multitel.be> Le lundi 01 d?cembre 2008 ? 08:43 +0300, Eugene Prokopiev a ?crit : > Hi, > > How can I setup network interface for Ekiga 3.0.1? It was possible > with Ekiga 2.0.12 in Edit - Prefernces - Protocol - Network Settings. > But now there are no such option :( It is not needed anymore. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From palos at post.sk Tue Dec 2 10:19:21 2008 From: palos at post.sk (Palo S.) Date: 02 Dec 2008 11:19:21 +0100 (CET) Subject: [Ekiga-list] \"remote user cleared the call\" problem Message-ID: <49350BA9.000001.32246@kamasutra> > > A cancel can be sent if you are using forking, ie 2 Ekiga registered > with the same account name, from 2 different IP addresses and ports. As > soon as one answers, a CANCEL is sent to the other one. > > Couldn\'t it be the case ? It could be that due to a problem with NAT a private IP communicates with the server as well as the public IP. I can probably only say after I sniff the communication. I will run a sniffer when I have time and let you know if I find something interesting. It is also interesting that with Ekiga 2.0.12 (on called side) it behaves differently - I have not had a look at d4 yet but it looked like caller (thought that) estabilished a SIP connection but called side not (it continued to ring on the called side, even after cancelling the call on the caller side). In any case, it worked fine with the previous server, so there must be a way to either fix or at least workaround the problem on the code level (either server or maybe also client) which would be nice at least because of ordinary users that do not know/wish to play around with port forwarding (all ports forwarding was originally enabled by the provider in this case, not by the user...) 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:dsandras at ekiga.net > > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list __________ BLOG - V?? denn?k umiestnen? na internete, v ktorom m??ete sprostredk?va? svoje my?lienky, z??itky a nov? inform?cie - http://blog.sme.sk/ From dsandras at seconix.com Tue Dec 2 12:09:31 2008 From: dsandras at seconix.com (Damien Sandras) Date: Tue, 02 Dec 2008 13:09:31 +0100 Subject: [Ekiga-list] \"remote user cleared the call\" problem In-Reply-To: <49350BA9.000001.32246@kamasutra> References: <49350BA9.000001.32246@kamasutra> Message-ID: <1228219771.4359.24.camel@scorpion.multitel.be> Le mardi 02 d?cembre 2008 ? 11:19 +0100, Palo S. a ?crit : > > > > A cancel can be sent if you are using forking, ie 2 Ekiga registered > > with the same account name, from 2 different IP addresses and ports. As > > soon as one answers, a CANCEL is sent to the other one. > > > > Couldn\'t it be the case ? > > It could be that due to a problem with NAT a private > IP communicates with the server as well as the public > IP. I can probably only say after I sniff the > communication. I will run a sniffer when I have time > and let you know if I find something interesting. It > is also interesting that with Ekiga 2.0.12 (on called > side) it behaves differently - I have not had a look > at d4 yet but it looked like caller (thought that) > estabilished a SIP connection but called side not > (it continued to ring on the called side, even after > cancelling the call on the caller side). > > In any case, it worked fine with the previous server, > so there must be a way to either fix or at least > workaround the problem on the code level (either server > or maybe also client) which would be nice at least because > of ordinary users that do not know/wish to play around > with port forwarding (all ports forwarding was > originally enabled by the provider in this case, not by > the user...) > If only I understood what really happens... Unfortunately, it is not the case :( -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From razametal at gmail.com Tue Dec 2 17:39:08 2008 From: razametal at gmail.com (RazaMetaL | Only The Good Die Young) Date: Tue, 2 Dec 2008 12:39:08 -0500 Subject: [Ekiga-list] [Ekiga-devel-list] Professional use of Ekiga : need someone for an interview In-Reply-To: <1228159930.4359.4.camel@scorpion.multitel.be> References: <1225875179.4990.197.camel@scorpion.multitel.be> <1226413684.4428.121.camel@scorpion.multitel.be> <1228159930.4359.4.camel@scorpion.multitel.be> Message-ID: On Mon, Dec 1, 2008 at 2:32 PM, Damien Sandras wrote: > Le dimanche 30 novembre 2008 ? 12:46 -0500, RazaMetaL | Only The Good > Die Young a ?crit : >> On Tue, Nov 11, 2008 at 9:28 AM, Damien Sandras wrote: [..] >> >> The article and interviews are at: >> >> http://www.computerworld.com/action/article.do?command=viewArticleBasic&taxonomyName=Networking+and+Internet&articleId=9120718&taxonomyId=16&pageNumber=2 >> >> Best regards, >> > > Thank you for the great article and the time you spent on it, it is much > appreciated! The credit it's for the article writer: Howard :) http://www.howardwen.com/ Regards, -- Linux User: 255902 Please avoid sending me Word or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html From zhangweiwu at realss.com Wed Dec 3 01:52:11 2008 From: zhangweiwu at realss.com (Zhang Weiwu) Date: Wed, 03 Dec 2008 09:52:11 +0800 Subject: [Ekiga-list] recommend a phone usable to ekiga and PSTN Message-ID: <4935E64B.6020908@realss.com> Hello. I am looking for having a new telephone for my office. I don't have much space so I wish to avoid having one telephone doing traditional landline call and another headset doing ekiga call. I am thinking having one telephone is enough. Idea A: Buy a traditional telephone that has a micophone and speaker jack plug. I plug it to my notebook so when I use ekiga the audio jack plug is used, when I do traditional phone call the RJ11 plug is used. Such a telephone does not require any digital parts and does not act as a USB device. First I am not sure if such device exists, then if it exists I don't know what keyword to search in ebay. Further I have an iBook,which has a special jack socket that have 4 contacts and handles both speaker & microphone (instead of other notebooks with two jack socket, one for microphone and one for speaker, each with 3 contacts). I am worrying maybe having a compatible device is difficult, then I need to buy a "splitter" to convert my 4-contact jack socket to two 3-contact jack sockets. Idea B: Buy a USB telephone that act as audio playback and audio capture device in Linux. First I am not sure if such device supports traditional telephone line. Then both two devices mentioned in http://wiki.ekiga.org/index.php/Controling_Ekiga_using_an_USB_phone are not found in ebay China. Suggestion? -- Real Softservice Huateng Tower, Unit 1788 Jia 302 3rd area of Jinsong, Chao Yang Tel: +86 (10) 8773 0650 ext 603 Mobile: 159 1111 7382 http://www.realss.com From enp at altlinux.org Wed Dec 3 05:18:43 2008 From: enp at altlinux.org (Eugene Prokopiev) Date: Wed, 3 Dec 2008 08:18:43 +0300 Subject: [Ekiga-list] Network interface for Ekiga 3.0.1 In-Reply-To: <1228166727.4359.6.camel@scorpion.multitel.be> References: <1228166727.4359.6.camel@scorpion.multitel.be> Message-ID: > > How can I setup network interface for Ekiga 3.0.1? It was possible > > with Ekiga 2.0.12 in Edit - Prefernces - Protocol - Network Settings. > > But now there are no such option :( > > > It is not needed anymore. But I have many strange problems with more than one ethernet interface, because Ekiga uses ip address from interface which is unknown for SIP server :( Is it possible to setup bind interface in cofiguration file? -- Thanks, Eugene Prokopiev From ma30002000 at yahoo.de Wed Dec 3 07:27:29 2008 From: ma30002000 at yahoo.de (Matthias Schneider) Date: Wed, 3 Dec 2008 07:27:29 +0000 (GMT) Subject: [Ekiga-list] ekiga pegs the CPU if started with the camera device turned off References: <20081124220935.GD7363@mcba11.phys.unsw.edu.au> <492BBA1F.6040408@thamnos.de> <805780.96526.qm@web25505.mail.ukl.yahoo.com> <20081125213131.GA14452@mcba11.phys.unsw.edu.au> <1227690597.4556.56.camel@scorpion.multitel.be> <20081126212844.GC20923@mcba11.phys.unsw.edu.au> Message-ID: <374597.68629.qm@web25503.mail.ukl.yahoo.com> Hi Michael, I have been trying to reproduce your issue but still no "luck". I enabled my camera, closed the call panel, left ekiga, unplugged the cam and restarted ekiga - still no 100% CPU. Probably it seems this issue only appears with certain display drivers and/or camera drivers? Maybe we will have to run an instrumented version on your PC. Do you think you could compile ekiga from the sources? Matthias ----- Urspr?ngliche Mail ---- > Von: Michael Ashley > An: Ekiga mailing list > Gesendet: Mittwoch, den 26. November 2008, 22:28:44 Uhr > Betreff: Re: [Ekiga-list] ekiga pegs the CPU if started with the camera device turned off > > Damien, > > > If there is no debug output, do you also reach 50% CPU in the same > > situation ? > > Yes. The CPU usage isn't just due to the last number of debug > messages. > > In fact, I see ekiga and Xorg together using up about 100% of the > CPU. The proportion used by each varies a little bit depending on > whether the debug output is on. > > Regards, Michael > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list From michel.memeteau at gmail.com Wed Dec 3 08:32:44 2008 From: michel.memeteau at gmail.com (michel memeteau) Date: Wed, 3 Dec 2008 09:32:44 +0100 Subject: [Ekiga-list] recommend a phone usable to ekiga and PSTN In-Reply-To: <4935E64B.6020908@realss.com> References: <4935E64B.6020908@realss.com> Message-ID: Isn't there a C idea ? Buy a hardware phone that does PSTN & SIP without a computer ? On Wed, Dec 3, 2008 at 2:52 AM, Zhang Weiwu wrote: > Hello. I am looking for having a new telephone for my office. I don't > have much space so I wish to avoid having one telephone doing > traditional landline call and another headset doing ekiga call. I am > thinking having one telephone is enough. > > Idea A: > Buy a traditional telephone that has a micophone and speaker jack plug. > I plug it to my notebook so when I use ekiga the audio jack plug is > used, when I do traditional phone call the RJ11 plug is used. Such a > telephone does not require any digital parts and does not act as a USB > device. First I am not sure if such device exists, then if it exists I > don't know what keyword to search in ebay. Further I have an iBook,which > has a special jack socket that have 4 contacts and handles both speaker > & microphone (instead of other notebooks with two jack socket, one for > microphone and one for speaker, each with 3 contacts). I am worrying > maybe having a compatible device is difficult, then I need to buy a > "splitter" to convert my 4-contact jack socket to two 3-contact jack > sockets. > > Idea B: > Buy a USB telephone that act as audio playback and audio capture device > in Linux. First I am not sure if such device supports traditional > telephone line. Then both two devices mentioned in > http://wiki.ekiga.org/index.php/Controling_Ekiga_using_an_USB_phone are > not found in ebay China. > > Suggestion? > > -- > Real Softservice > > Huateng Tower, Unit 1788 > Jia 302 3rd area of Jinsong, Chao Yang > > Tel: +86 (10) 8773 0650 ext 603 > Mobile: 159 1111 7382 > http://www.realss.com > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > -- %<------------------------------------------------------->% Michel memeteau Blog 0.2 : http://memeteau.free.fr Fixe : 0974763294 Mobile : 0624808051 VOIP | Visio: sip:freechelmi at ippi.fr jabber/GTalk : xmpp:freechelmi at jabber.fr -------------- next part -------------- An HTML attachment was scrubbed... URL: From dsandras at seconix.com Wed Dec 3 08:43:39 2008 From: dsandras at seconix.com (Damien Sandras) Date: Wed, 03 Dec 2008 09:43:39 +0100 Subject: [Ekiga-list] Network interface for Ekiga 3.0.1 In-Reply-To: References: <1228166727.4359.6.camel@scorpion.multitel.be> Message-ID: <1228293819.17445.2.camel@scorpion.multitel.be> Le mercredi 03 d?cembre 2008 ? 08:18 +0300, Eugene Prokopiev a ?crit : > > > How can I setup network interface for Ekiga 3.0.1? It was possible > > > with Ekiga 2.0.12 in Edit - Prefernces - Protocol - Network Settings. > > > But now there are no such option :( > > > > > > It is not needed anymore. > > But I have many strange problems with more than one ethernet > interface, because Ekiga uses ip address from interface which is > unknown for SIP server :( > Can u post a -d 4 output? > Is it possible to setup bind interface in cofiguration file? Not anymore... -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From m.ashley at unsw.edu.au Wed Dec 3 08:19:22 2008 From: m.ashley at unsw.edu.au (Michael Ashley) Date: Wed, 3 Dec 2008 19:19:22 +1100 Subject: [Ekiga-list] ekiga pegs the CPU if started with the camera device turned off In-Reply-To: <374597.68629.qm@web25503.mail.ukl.yahoo.com> References: <20081124220935.GD7363@mcba11.phys.unsw.edu.au> <492BBA1F.6040408@thamnos.de> <805780.96526.qm@web25505.mail.ukl.yahoo.com> <20081125213131.GA14452@mcba11.phys.unsw.edu.au> <1227690597.4556.56.camel@scorpion.multitel.be> <20081126212844.GC20923@mcba11.phys.unsw.edu.au> <374597.68629.qm@web25503.mail.ukl.yahoo.com> Message-ID: <20081203081922.GB2150@mcba11.phys.unsw.edu.au> Hi Matthias, Thank you for investigating this issue further. Yes, I could compile ekiga from sources. I did this earlier with 3.0.1. It took me a while to track down all the needed libraries, but I eventually made a working version. Regards, Michael On Wed, Dec 03, 2008 at 07:27:29AM +0000, Matthias Schneider wrote: > Hi Michael, > > I have been trying to reproduce your issue but still no "luck". I enabled my camera, > closed the call panel, left ekiga, unplugged the cam and restarted ekiga - still no 100% CPU. > Probably it seems this issue only appears with certain display drivers and/or camera drivers? > Maybe we will have to run an instrumented version on your PC. Do you think you could compile > ekiga from the sources? > > Matthias > > > > ----- Urspr?ngliche Mail ---- > > Von: Michael Ashley > > An: Ekiga mailing list > > Gesendet: Mittwoch, den 26. November 2008, 22:28:44 Uhr > > Betreff: Re: [Ekiga-list] ekiga pegs the CPU if started with the camera device turned off > > > > Damien, > > > > > If there is no debug output, do you also reach 50% CPU in the same > > > situation ? > > > > Yes. The CPU usage isn't just due to the last number of debug > > messages. > > > > In fact, I see ekiga and Xorg together using up about 100% of the > > CPU. The proportion used by each varies a little bit depending on > > whether the debug output is on. > > > > Regards, Michael > > _______________________________________________ > > ekiga-list mailing list > > ekiga-list at gnome.org > > http://mail.gnome.org/mailman/listinfo/ekiga-list > > > > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list From enp at altlinux.org Wed Dec 3 11:19:33 2008 From: enp at altlinux.org (Eugene Prokopiev) Date: Wed, 3 Dec 2008 14:19:33 +0300 Subject: [Ekiga-list] Network interface for Ekiga 3.0.1 In-Reply-To: <1228293819.17445.2.camel@scorpion.multitel.be> References: <1228166727.4359.6.camel@scorpion.multitel.be> <1228293819.17445.2.camel@scorpion.multitel.be> Message-ID: 2008/12/3, Damien Sandras: > Le mercredi 03 d?cembre 2008 ? 08:18 +0300, Eugene Prokopiev a ?crit : > > > > > How can I setup network interface for Ekiga 3.0.1? It was possible > > > > with Ekiga 2.0.12 in Edit - Prefernces - Protocol - Network Settings. > > > > But now there are no such option :( > > > > > > > > > It is not needed anymore. > > > > But I have many strange problems with more than one ethernet > > interface, because Ekiga uses ip address from interface which is > > unknown for SIP server :( > > > > > Can u post a -d 4 output bzipped log is attached -- Thanks, Eugene Prokopiev -------------- next part -------------- A non-text attachment was scrubbed... Name: ekiga.log.bz2 Type: application/x-bzip2 Size: 10142 bytes Desc: not available URL: From law_ence.dev at ntlworld.com Wed Dec 3 15:25:17 2008 From: law_ence.dev at ntlworld.com (ael) Date: Wed, 03 Dec 2008 15:25:17 +0000 Subject: [Ekiga-list] recommend a phone usable to ekiga and PSTN In-Reply-To: <4935E64B.6020908@realss.com> References: <4935E64B.6020908@realss.com> Message-ID: <4936A4DD.5080101@ntlworld.com> Zhang Weiwu wrote: > Hello. I am looking for having a new telephone for my office. I don't > have much space so I wish to avoid having one telephone doing > traditional landline call and another headset doing ekiga call. I am > thinking having one telephone is enough. Not an ekiga solution, but compatible: look into the Handytone adaptor series from Grandstream. Works here. www.grandstream.com IIRC. ael From dsandras at seconix.com Wed Dec 3 17:08:05 2008 From: dsandras at seconix.com (Damien Sandras) Date: Wed, 03 Dec 2008 18:08:05 +0100 Subject: [Ekiga-list] Network interface for Ekiga 3.0.1 In-Reply-To: References: <1228166727.4359.6.camel@scorpion.multitel.be> <1228293819.17445.2.camel@scorpion.multitel.be> Message-ID: <1228324085.17445.45.camel@scorpion.multitel.be> Le mercredi 03 d?cembre 2008 ? 14:19 +0300, Eugene Prokopiev a ?crit : > 2008/12/3, Damien Sandras: > > Le mercredi 03 d?cembre 2008 ? 08:18 +0300, Eugene Prokopiev a ?crit : > > > > > > > How can I setup network interface for Ekiga 3.0.1? It was possible > > > > > with Ekiga 2.0.12 in Edit - Prefernces - Protocol - Network Settings. > > > > > But now there are no such option :( > > > > > > > > > > > > It is not needed anymore. > > > > > > But I have many strange problems with more than one ethernet > > > interface, because Ekiga uses ip address from interface which is > > > unknown for SIP server :( > > > > > > > > > Can u post a -d 4 output > > bzipped log is attached Apparently CallWeaver deals as badly as Asterisk with forked INVITEs. Can you check if it works with recent snapshots from http://snapshots.ekiga.net ? -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From listsm at yahoo.ca Wed Dec 3 23:11:58 2008 From: listsm at yahoo.ca (Mailing Lists) Date: Wed, 3 Dec 2008 15:11:58 -0800 (PST) Subject: [Ekiga-list] win32 binaries Message-ID: <196935.87982.qm@web111010.mail.gq1.yahoo.com> Could someone please point me to an archive page for an old 2.0.11 or 2.0.12 binary and matching support libs for win32? I've got a friend in windows land who's having problems with the win32 beta snapshots, and I can't find anything for her to fall back to on the web site. (She blew away her old (working) ekiga install). Thanks, James Georgas __________________________________________________________________ Connect with friends from any web browser - no download required. Try the new Yahoo! Canada Messenger for the Web BETA at http://ca.messenger.yahoo.com/webmessengerpromo.php -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhangweiwu at realss.com Thu Dec 4 00:29:19 2008 From: zhangweiwu at realss.com (Zhang Weiwu) Date: Thu, 04 Dec 2008 08:29:19 +0800 Subject: [Ekiga-list] recommend a phone usable to ekiga and PSTN In-Reply-To: References: <4935E64B.6020908@realss.com> Message-ID: <4937245F.4080206@realss.com> michel memeteau wrote: > Isn't there a C idea ? Buy a hardware phone that does PSTN & SIP > without a computer ? Oh I didn't know it is possible! From enp at altlinux.org Thu Dec 4 08:06:03 2008 From: enp at altlinux.org (Eugene Prokopiev) Date: Thu, 4 Dec 2008 11:06:03 +0300 Subject: [Ekiga-list] Network interface for Ekiga 3.0.1 In-Reply-To: <1228324085.17445.45.camel@scorpion.multitel.be> References: <1228166727.4359.6.camel@scorpion.multitel.be> <1228293819.17445.2.camel@scorpion.multitel.be> <1228324085.17445.45.camel@scorpion.multitel.be> Message-ID: > Apparently CallWeaver deals as badly as Asterisk with forked INVITEs. > > Can you check if it works with recent snapshots from > http://snapshots.ekiga.net ? I can't compile ekiga-snapshot-latest.tar.gz with opal-snapshot-latest.tar.gz due to: ../../../../lib/engine/components/opal/sip-endpoint.cpp: In member function 'virtual SIPURL Opal::Sip::EndPoint::GetRegisteredPartyName(const SIPURL&)': ../../../../lib/engine/components/opal/sip-endpoint.cpp:1014: error: 'class SIPHandler' has no member named 'GetAddressOfRecord' -- Thanks, Eugene Prokopiev From dsandras at seconix.com Thu Dec 4 08:48:13 2008 From: dsandras at seconix.com (Damien Sandras) Date: Thu, 04 Dec 2008 09:48:13 +0100 Subject: [Ekiga-list] Network interface for Ekiga 3.0.1 In-Reply-To: References: <1228166727.4359.6.camel@scorpion.multitel.be> <1228293819.17445.2.camel@scorpion.multitel.be> <1228324085.17445.45.camel@scorpion.multitel.be> Message-ID: <1228380493.17445.58.camel@scorpion.multitel.be> Le jeudi 04 d?cembre 2008 ? 11:06 +0300, Eugene Prokopiev a ?crit : > > Apparently CallWeaver deals as badly as Asterisk with forked INVITEs. > > > > Can you check if it works with recent snapshots from > > http://snapshots.ekiga.net ? > > I can't compile ekiga-snapshot-latest.tar.gz with > opal-snapshot-latest.tar.gz due to: > > ../../../../lib/engine/components/opal/sip-endpoint.cpp: In member > function 'virtual SIPURL > Opal::Sip::EndPoint::GetRegisteredPartyName(const SIPURL&)': > ../../../../lib/engine/components/opal/sip-endpoint.cpp:1014: error: > 'class SIPHandler' has no member named 'GetAddressOfRecord' > Go here : http://snapshots.ekiga.net/snapshots/sources/archives/ And take ptlib/opal and ekiga from 20081203. It should work. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From enp at altlinux.org Thu Dec 4 09:33:27 2008 From: enp at altlinux.org (Eugene Prokopiev) Date: Thu, 4 Dec 2008 12:33:27 +0300 Subject: [Ekiga-list] Network interface for Ekiga 3.0.1 In-Reply-To: <1228380493.17445.58.camel@scorpion.multitel.be> References: <1228166727.4359.6.camel@scorpion.multitel.be> <1228293819.17445.2.camel@scorpion.multitel.be> <1228324085.17445.45.camel@scorpion.multitel.be> <1228380493.17445.58.camel@scorpion.multitel.be> Message-ID: > > I can't compile ekiga-snapshot-latest.tar.gz with > > opal-snapshot-latest.tar.gz due to: > > > > ../../../../lib/engine/components/opal/sip-endpoint.cpp: In member > > function 'virtual SIPURL > > Opal::Sip::EndPoint::GetRegisteredPartyName(const SIPURL&)': > > ../../../../lib/engine/components/opal/sip-endpoint.cpp:1014: error: > > 'class SIPHandler' has no member named 'GetAddressOfRecord' > > > > > Go here : > http://snapshots.ekiga.net/snapshots/sources/archives/ > > And take ptlib/opal and ekiga from 20081203. It should work. ekiga-snapshot-20081203.tar.gz is the same as ekiga-snapshot-latest.tar.gz and opal-snapshot-20081203.tar.gz is the same as opal-snapshot-latest.tar.gz grep -r GetAddressOfRecord opal/ is empty -- Thanks, Eugene Prokopiev From dsandras at seconix.com Thu Dec 4 10:16:35 2008 From: dsandras at seconix.com (Damien Sandras) Date: Thu, 04 Dec 2008 11:16:35 +0100 Subject: [Ekiga-list] Network interface for Ekiga 3.0.1 In-Reply-To: References: <1228166727.4359.6.camel@scorpion.multitel.be> <1228293819.17445.2.camel@scorpion.multitel.be> <1228324085.17445.45.camel@scorpion.multitel.be> <1228380493.17445.58.camel@scorpion.multitel.be> Message-ID: <1228385795.17445.65.camel@scorpion.multitel.be> Le jeudi 04 d?cembre 2008 ? 12:33 +0300, Eugene Prokopiev a ?crit : > > > I can't compile ekiga-snapshot-latest.tar.gz with > > > opal-snapshot-latest.tar.gz due to: > > > > > > ../../../../lib/engine/components/opal/sip-endpoint.cpp: In member > > > function 'virtual SIPURL > > > Opal::Sip::EndPoint::GetRegisteredPartyName(const SIPURL&)': > > > ../../../../lib/engine/components/opal/sip-endpoint.cpp:1014: error: > > > 'class SIPHandler' has no member named 'GetAddressOfRecord' > > > > > > > > > Go here : > > http://snapshots.ekiga.net/snapshots/sources/archives/ > > > > And take ptlib/opal and ekiga from 20081203. It should work. > > ekiga-snapshot-20081203.tar.gz is the same as > ekiga-snapshot-latest.tar.gz and opal-snapshot-20081203.tar.gz is the > same as opal-snapshot-latest.tar.gz > > grep -r GetAddressOfRecord opal/ is empty > You are right, I'll fix it this week-end. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From calie at uwaterloo.ca Sat Dec 6 10:46:46 2008 From: calie at uwaterloo.ca (Colin Alie) Date: Sat, 6 Dec 2008 21:46:46 +1100 Subject: [Ekiga-list] Ekiga version 2.0.12 no longer compatible with ekiga.net? Message-ID: <200812062146.47117.calie@uwaterloo.ca> Good evening, I'd been using Ekiga 2.0.12 (Ubuntu 8.04) in my current setup from the beginning of October. Some details regarding my configuration: - DSL modem router connected to the Internet via PPPoE - laptop connected to the modem's ethernet port - modem is doing NAT w/ IP masquerading - STUN enabled in Ekiga with stun.ekiga.net given as the STUN server - Ekiga detects NAT as port-restricted Up until the "upgrade" to ekiga.net, I was using my ekiga.net account to make calls to the echo test (500 at ekiga.net) and to toll-free numbers in North America (sip;*0131800xxxxxxx at ekiga.net) and using a different account for making PC-to-phone calls. Since the upgrade, I can make calls but I don't receive audio or video. For example, I'll dial the echo test (500 at ekiga.net) and connect successfully but I don't hear the recorded message. As I speak into the microphone, the recording level at the bottom of the interface increases and decreases accordingly but no sound is echoed. The outgoing audio and video bitrates average at about 8 kB/s but the incoming audio and video bitrates stay fixed at 0.00. My current feeling is that my current issues are related to the changes that were make with ekiga.net as: - my computer systems haven't changed - I first noticed problems with ekiga.net on November 13th (i.e., after the upgrade) - my ability to use Ekiga to make calls with my other SIP account is unchanged I've included below the output from an Ekiga session (ekiga -d 4 &) where I called 500 at ekiga.net while registered with ekiga.net. Please let me know if there's any additional debugging assistance that I can provide. Until next time, Colin. ---- Begin debugging output ---- 2008/12/04 22:22:32.475 0:00.428 ekiga Detected audio plugins: ALSA 2008/12/04 22:22:32.476 0:00.428 ekiga Detected video plugins: Picture,V4L2,V4L 2008/12/04 22:22:32.476 0:00.428 ekiga Detected audio plugins: ALSA 2008/12/04 22:22:32.476 0:00.428 ekiga Detected video plugins: Picture,V4L2,V4L 2008/12/04 22:22:32.592 0:00.544 ekiga Detected the following audio input devices: Default,HDA Intel with plugin ALSA 2008/12/04 22:22:32.592 0:00.544 ekiga Detected the following audio output devices: Default,HDA Intel with plugin ALSA 2008/12/04 22:22:32.592 0:00.544 ekiga Detected the following video input devices: No device found with plugin V4L2 2008/12/04 22:22:32.593 0:00.545 ekiga Detected the following audio input devices: Default,HDA Intel with plugin ALSA 2008/12/04 22:22:32.593 0:00.545 ekiga Detected the following audio output devices: Default,HDA Intel with plugin ALSA 2008/12/04 22:22:32.593 0:00.545 ekiga Detected the following video input devices: No device found with plugin V4L2 2008/12/04 22:22:32.915 0:00.867 ekiga Ekiga version 2.0.12 2008/12/04 22:22:32.915 0:00.867 ekiga OPAL version 2.2.11 2008/12/04 22:22:32.916 0:00.868 ekiga PWLIB version 1.10.10 2008/12/04 22:22:32.917 0:00.869 ekiga GNOME support enabled 2008/12/04 22:22:32.918 0:00.870 ekiga Fullscreen support enabled 2008/12/04 22:22:32.918 0:00.870 ekiga DBUS support enabled 2008/12/04 22:22:32.921 0:00.873 ekiga Set TCP port range to 30000:30010 2008/12/04 22:22:32.921 0:00.873 ekiga Set RTP port range to 5000:5059 2008/12/04 22:22:32.922 0:00.874 ekiga Set UDP port range to 5060:5100 2008/12/04 22:22:33.043 0:00.995 ekiga AVAHI Adding service Colin Alie (ekiga:15714): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.16.3/gobject/gsignal.c:1715: handler `2858' of instance `0x84e0168' is not blocked 2008/12/04 22:24:31.788 1:59.740 SIP Handler:85de940 Ekiga Creating Sound Channel 2008/12/04 22:24:32.127 2:00.079 SIP Handler:85de940 Ekiga Creating Sound Channel 2008/12/04 22:24:32.503 2:00.455 SIP Handler:85de940 GMPCSSEndpoint PCSS connection established 2008/12/04 22:24:32.503 2:00.455 SIP Handler:85de940 GMManager Will establish the connection 2008/12/04 22:24:32.513 2:00.465 SIP Handler:85de940 GMSIPEndpoint SIP connection established 2008/12/04 22:24:32.538 2:00.490 SIP Handler:85de940 GMManager Will establish the connection 2008/12/04 22:24:57.912 2:25.864 OnRelease:8510f20 GMPCSSEndpoint PCSS connection released 2008/12/04 22:24:57.912 2:25.864 OnRelease:8510f20 GMManager Will release the connection 2008/12/04 22:24:58.286 2:26.239 OnRelease:84849b8 GMSIPEndpoint SIP connection released 2008/12/04 22:24:58.336 2:26.288 OnRelease:84849b8 GMManager Will release the connection From billcollins1.2007 at gmail.com Sun Dec 7 01:00:18 2008 From: billcollins1.2007 at gmail.com (Bill Collins) Date: Sat, 6 Dec 2008 20:00:18 -0500 Subject: [Ekiga-list] No Sound Message-ID: <33efb16e0812061700m274f4fedna635d04fd837e67f@mail.gmail.com> I have spent considerable time researching the sound problem to no avail. I now turn to the true experts. I have listed as much as I know to help. If more is needed please advise. Also I'm a beginner at this. tia Bill Collins Dell Inspiron B130 1 gb ram Ubuntu 8.04.1 GNOME ekiga 2.0.12 Sound works perfectly well for movies and music. Logitech Quickcam Pro 9000 Video works perfectly well. No sound. Using default audio input and output but did not get any sound return when speaking into microphone. Did "Test 1 2 3 Ekiga Rocks" Nothing comes back. 00:1b.0 Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller (rev 03) bill at oldcity:~$ ekiga -d 5 2008/12/06 18:29:56.157 0:00.527 ekiga Detected audio plugins: ALSA 2008/12/06 18:29:56.158 0:00.528 ekiga Detected video plugins: Picture,V4L,V4L2 2008/12/06 18:29:56.159 0:00.529 ekiga Detected audio plugins: ALSA 2008/12/06 18:29:56.159 0:00.529 ekiga Detected video plugins: Picture,V4L,V4L2 2008/12/06 18:29:56.298 0:00.668 ekiga Detected the following audio input devices: Default,HDA Intel,USB Device 0x46d:0x990 with plugin ALSA 2008/12/06 18:29:56.299 0:00.669 ekiga Detected the following audio output devices: Default,HDA Intel with plugin ALSA 2008/12/06 18:29:56.300 0:00.670 ekiga Detected the following video input devices: UVC Camera (046d:0990) with plugin V4L2 2008/12/06 18:29:56.301 0:00.671 ekiga Detected the following audio input devices: Default,HDA Intel,USB Device 0x46d:0x990 with plugin ALSA 2008/12/06 18:29:56.301 0:00.672 ekiga Detected the following audio output devices: Default,HDA Intel with plugin ALSA 2008/12/06 18:29:56.302 0:00.672 ekiga Detected the following video input devices: UVC Camera (046d:0990) with plugin V4L2 2008/12/06 18:29:56.965 0:01.335 ekiga Ekiga version 2.0.12 2008/12/06 18:29:56.966 0:01.336 ekiga OPAL version 2.2.11 2008/12/06 18:29:56.966 0:01.336 ekiga PWLIB version 1.10.10 2008/12/06 18:29:56.967 0:01.337 ekiga GNOME support enabled 2008/12/06 18:29:56.968 0:01.338 ekiga Fullscreen support enabled 2008/12/06 18:29:56.969 0:01.339 ekiga DBUS support enabled 2008/12/06 18:29:56.974 0:01.348 ekiga Set TCP port range to 30000:30010 2008/12/06 18:29:56.978 0:01.348 ekiga Set RTP port range to 5000:5059 2008/12/06 18:29:56.979 0:01.349 ekiga Set UDP port range to 5060:5100 2008/12/06 18:29:57.157 0:01.527 ekiga AVAHI Adding service bill collins *** Page aborts here. -------------- next part -------------- An HTML attachment was scrubbed... URL: From dsandras at seconix.com Sun Dec 7 16:08:24 2008 From: dsandras at seconix.com (Damien Sandras) Date: Sun, 07 Dec 2008 17:08:24 +0100 Subject: [Ekiga-list] Ekiga version 2.0.12 no longer compatible with ekiga.net? In-Reply-To: <200812062146.47117.calie@uwaterloo.ca> References: <200812062146.47117.calie@uwaterloo.ca> Message-ID: <1228666104.17134.79.camel@scorpion.multitel.be> Le samedi 06 d?cembre 2008 ? 21:46 +1100, Colin Alie a ?crit : > Good evening, > > I'd been using Ekiga 2.0.12 (Ubuntu 8.04) in my current setup from the > beginning of October. Some details regarding my configuration: > > - DSL modem router connected to the Internet via PPPoE > - laptop connected to the modem's ethernet port > - modem is doing NAT w/ IP masquerading > - STUN enabled in Ekiga with stun.ekiga.net given as the STUN server > - Ekiga detects NAT as port-restricted > > Up until the "upgrade" to ekiga.net, I was using my ekiga.net account to make > calls to the echo test (500 at ekiga.net) and to toll-free numbers in North > America (sip;*0131800xxxxxxx at ekiga.net) and using a different account for > making PC-to-phone calls. > > Since the upgrade, I can make calls but I don't receive audio or video. For > example, I'll dial the echo test (500 at ekiga.net) and connect successfully but > I don't hear the recorded message. As I speak into the microphone, the > recording level at the bottom of the interface increases and decreases > accordingly but no sound is echoed. The outgoing audio and video bitrates > average at about 8 kB/s but the incoming audio and video bitrates stay fixed > at 0.00. > > My current feeling is that my current issues are related to the changes that > were make with ekiga.net as: > - my computer systems haven't changed > - I first noticed problems with ekiga.net on November 13th (i.e., after the > upgrade) > - my ability to use Ekiga to make calls with my other SIP account is unchanged > > I've included below the output from an Ekiga session (ekiga -d 4 &) where I > called 500 at ekiga.net while registered with ekiga.net. Please let me know if > there's any additional debugging assistance that I can provide. The debug output is incomplete. Maybe you are missing a ptrace package or something so. Bad news for you : Ekiga 2.x still works with ekiga.net... Nothing significant has changed from that point of view. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From dsandras at seconix.com Sun Dec 7 16:09:22 2008 From: dsandras at seconix.com (Damien Sandras) Date: Sun, 07 Dec 2008 17:09:22 +0100 Subject: [Ekiga-list] No Sound In-Reply-To: <33efb16e0812061700m274f4fedna635d04fd837e67f@mail.gmail.com> References: <33efb16e0812061700m274f4fedna635d04fd837e67f@mail.gmail.com> Message-ID: <1228666162.17134.81.camel@scorpion.multitel.be> Le samedi 06 d?cembre 2008 ? 20:00 -0500, Bill Collins a ?crit : > I have spent considerable time researching the sound problem to no > avail. I now turn > to the true experts. I have listed as much as I know to help. If more > is needed > please advise. Also I'm a beginner at this. > tia > Bill Collins > > Dell Inspiron B130 1 gb ram > Ubuntu 8.04.1 GNOME ekiga 2.0.12 > > Sound works perfectly well for movies and music. > > Logitech Quickcam Pro 9000 > > Video works perfectly well. No sound. Using default audio input and > output but > did not get any sound return when speaking into microphone. Did "Test > 1 2 3 Ekiga Rocks" Nothing comes back. > Open your mixer (gnome-mixer or another one) and make sure that the recording source is set to the Mic entry. Your problem is a simple mixer settings related problem. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From dsandras at seconix.com Sun Dec 7 16:24:57 2008 From: dsandras at seconix.com (Damien Sandras) Date: Sun, 07 Dec 2008 17:24:57 +0100 Subject: [Ekiga-list] Network interface for Ekiga 3.0.1 In-Reply-To: <1228385795.17445.65.camel@scorpion.multitel.be> References: <1228166727.4359.6.camel@scorpion.multitel.be> <1228293819.17445.2.camel@scorpion.multitel.be> <1228324085.17445.45.camel@scorpion.multitel.be> <1228380493.17445.58.camel@scorpion.multitel.be> <1228385795.17445.65.camel@scorpion.multitel.be> Message-ID: <1228667097.17134.83.camel@scorpion.multitel.be> Le jeudi 04 d?cembre 2008 ? 11:16 +0100, Damien Sandras a ?crit : > Le jeudi 04 d?cembre 2008 ? 12:33 +0300, Eugene Prokopiev a ?crit : > > > > I can't compile ekiga-snapshot-latest.tar.gz with > > > > opal-snapshot-latest.tar.gz due to: > > > > > > > > ../../../../lib/engine/components/opal/sip-endpoint.cpp: In member > > > > function 'virtual SIPURL > > > > Opal::Sip::EndPoint::GetRegisteredPartyName(const SIPURL&)': > > > > ../../../../lib/engine/components/opal/sip-endpoint.cpp:1014: error: > > > > 'class SIPHandler' has no member named 'GetAddressOfRecord' > > > > > > > > > > > > > Go here : > > > http://snapshots.ekiga.net/snapshots/sources/archives/ > > > > > > And take ptlib/opal and ekiga from 20081203. It should work. > > > > ekiga-snapshot-20081203.tar.gz is the same as > > ekiga-snapshot-latest.tar.gz and opal-snapshot-20081203.tar.gz is the > > same as opal-snapshot-latest.tar.gz > > > > grep -r GetAddressOfRecord opal/ is empty > > > > You are right, I'll fix it this week-end. opal/include/sip/handlers.h: virtual const SIPURL & GetAddressOfRecord() Can you double check ? Actually, there *is* that method in handlers.h... -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From palos at post.sk Sun Dec 7 16:55:28 2008 From: palos at post.sk (Palo S.) Date: 07 Dec 2008 17:55:28 +0100 (CET) Subject: [Ekiga-list] Ekiga version 2.0.12 no longer compatiblewith ekiga.net? Message-ID: <493C0000.000003.05137@kamasutra> This looks like a NAT issue. You can have a look at the \"remote user cleared the call\" thread that I opened in November - that is another example when the NAT settings that worked with the old server stopped working with the new one. Maybe a change in NAT settings could fix your problem as it was in my case. (I still did not find time to run a sniffer to find out what exactly was going on there) Palo __________ http://www.pnp.sk - pridajte svoje fotky na PaciNepaci From edunagin at gmail.com Sun Dec 7 17:22:29 2008 From: edunagin at gmail.com (Edward Dunagin) Date: Sun, 7 Dec 2008 10:22:29 -0700 Subject: [Ekiga-list] No Sound In-Reply-To: <1228666162.17134.81.camel@scorpion.multitel.be> References: <33efb16e0812061700m274f4fedna635d04fd837e67f@mail.gmail.com> <1228666162.17134.81.camel@scorpion.multitel.be> Message-ID: <2af451740812070922t104958ceh439df6c95b5bacdc@mail.gmail.com> Edward Dunagin-Dunigan Bozeman, MT 59718 mobile 406-570-0992 Land line 406-556-7282 EKIGA: sip:edunagin at ekiga.net http://doas.montanalinux.org On Sun, Dec 7, 2008 at 9:09 AM, Damien Sandras wrote: > Le samedi 06 d?cembre 2008 ? 20:00 -0500, Bill Collins a ?crit : >> I have spent considerable time researching the sound problem to no >> avail. I now turn >> to the true experts. I have listed as much as I know to help. If more >> is needed >> please advise. Also I'm a beginner at this. >> tia >> Bill Collins >> >> Dell Inspiron B130 1 gb ram >> Ubuntu 8.04.1 GNOME ekiga 2.0.12 >> >> Sound works perfectly well for movies and music. >> >> Logitech Quickcam Pro 9000 >> >> Video works perfectly well. No sound. Using default audio input and >> output but >> did not get any sound return when speaking into microphone. Did "Test >> 1 2 3 Ekiga Rocks" Nothing comes back. >> > > Open your mixer (gnome-mixer or another one) and make sure that the > recording source is set to the Mic entry. Your problem is a simple mixer > settings related problem. > -- > _ Damien Sandras That maybe so, BUT which mixer??? I use Linux, particularly Ubuntu8.10. There are three different mixer settings on my system and the only one I added was the Gnome-alsamixer. They all seem to effect the system, so if one is set wrong, then all of it is wrong. I am an old Linux user and I think this is the reason for all the problems with sound, and it might be all the problems with video. So, my advice is if you have more than one mixer and you probably do, make sure they are ALL set to the settings that you want, sound and video. Peace.....................ed From f.vonbock at gmail.com Sun Dec 7 19:09:05 2008 From: f.vonbock at gmail.com (Fedor vonBock) Date: Sun, 7 Dec 2008 22:09:05 +0300 Subject: [Ekiga-list] can't compile ekiga 3.0.1 ubuntu hardy Message-ID: Hi, I used this site (http://wiki.ekiga.org/index.php/Talk:Additional_Information#PTLIB) to help compile and install ekiga 3.0.1. However, i notice a difference in the final configuration where the directories for the PTLIB and the OPAL do not show. I've included my output below and it clearly doesn't show the PTLIB and OPAL directories. I tried to compile ekiga later on with make and i got an error ================ Final configuration =================== Installing into prefix : /usr GNOME support : enabled GConf support : enabled Evolution-Data-Server support : enabled NOTIFY support : disabled LDAP support : enabled XVideo support : enabled H.323 support : yes SIP support : yes DBUS support : enabled DBUS service support : enabled mDNS/DNS-SD support : enabled GStreamer support : disabled KAddressBook support : disabled KDE support : disabled XCAP support : disabled OS Type : linux-gnu Machine Type : i686 Byte Order : little endian From enp at altlinux.org Mon Dec 8 06:05:35 2008 From: enp at altlinux.org (Eugene Prokopiev) Date: Mon, 8 Dec 2008 09:05:35 +0300 Subject: [Ekiga-list] Network interface for Ekiga 3.0.1 In-Reply-To: <1228667097.17134.83.camel@scorpion.multitel.be> References: <1228293819.17445.2.camel@scorpion.multitel.be> <1228324085.17445.45.camel@scorpion.multitel.be> <1228380493.17445.58.camel@scorpion.multitel.be> <1228385795.17445.65.camel@scorpion.multitel.be> <1228667097.17134.83.camel@scorpion.multitel.be> Message-ID: > > You are right, I'll fix it this week-end. > > opal/include/sip/handlers.h: virtual const SIPURL & > GetAddressOfRecord() > > Can you double check ? > > Actually, there *is* that method in handlers.h... I can't see that method: $ wget http://snapshots.ekiga.net/snapshots/sources/archives/opal-snapshot-20081207.tar.gz $ tar -zxf opal-snapshot-20081207.tar.gz $ grep GetAddressOfRecord opal/include/sip/handlers.h $ grep -r GetAddressOfRecord opal/ $ -- Thanks, Eugene Prokopiev From dsandras at seconix.com Mon Dec 8 06:49:24 2008 From: dsandras at seconix.com (Damien Sandras) Date: Mon, 08 Dec 2008 07:49:24 +0100 Subject: [Ekiga-list] can't compile ekiga 3.0.1 ubuntu hardy In-Reply-To: References: Message-ID: <1228718964.31538.0.camel@scorpion.multitel.be> Le dimanche 07 d?cembre 2008 ? 22:09 +0300, Fedor vonBock a ?crit : > Hi, > > I used this site > (http://wiki.ekiga.org/index.php/Talk:Additional_Information#PTLIB) to > help compile and install ekiga 3.0.1. However, i notice a difference > in the final configuration where the directories for the PTLIB and the > OPAL do not show. I've included my output below and it clearly > doesn't show the PTLIB and OPAL directories. > > > I tried to compile ekiga later on with make and i got an error > > > > > > ================ Final configuration =================== > Installing into prefix : /usr > > GNOME support : enabled > GConf support : enabled > Evolution-Data-Server support : enabled > NOTIFY support : disabled > LDAP support : enabled > > XVideo support : enabled > > H.323 support : yes > SIP support : yes > > DBUS support : enabled > DBUS service support : enabled > mDNS/DNS-SD support : enabled > GStreamer support : disabled > KAddressBook support : disabled > KDE support : disabled > XCAP support : disabled > > OS Type : linux-gnu > Machine Type : i686 > Byte Order : little endian Where do you see an error ? -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From calie at uwaterloo.ca Mon Dec 8 11:17:32 2008 From: calie at uwaterloo.ca (Colin Alie) Date: Mon, 8 Dec 2008 22:17:32 +1100 Subject: [Ekiga-list] Ekiga version 2.0.12 no longer compatible with ekiga.net? Message-ID: <200812082217.32235.calie@uwaterloo.ca> Good evening Damien and Palo, Thanks for your replies. Damien, I'm sorry the expected debugging information was not included in my last message. I've since installed the correct libraries. I've attached to this message the file ekiga.log which contains the output from a session in which the following actions were taken: - started ekiga ($ ekiga -d 4 2> ekiga.log) - Edit-->Accounts and activated ekiga.net account - dialed 500 at ekiga.net - waited for call to connect and said a few words - terminated call - quit Ekiga Palo, I read the thread "remote user cleared the call" that you started late November. I've taken your comment regarding NAT to heart. Connecting my laptop directly to the Internet was on my list of things to try as I'm able to use Ekiga on my workstation at work which has a public IP address. One more thing...whenever I register to any account using Ekiga, I always see two messages in the General History confirming registration. Does this imply anything? Anyway, thanks for your help. Until next time, Colin. -------------- next part -------------- A non-text attachment was scrubbed... Name: ekiga.log.gz Type: application/x-gzip Size: 10406 bytes Desc: not available URL: From billcollins1.2007 at gmail.com Mon Dec 8 14:39:47 2008 From: billcollins1.2007 at gmail.com (Bill Collins) Date: Mon, 8 Dec 2008 09:39:47 -0500 Subject: [Ekiga-list] No Sound In-Reply-To: <2af451740812070922t104958ceh439df6c95b5bacdc@mail.gmail.com> References: <33efb16e0812061700m274f4fedna635d04fd837e67f@mail.gmail.com> <1228666162.17134.81.camel@scorpion.multitel.be> <2af451740812070922t104958ceh439df6c95b5bacdc@mail.gmail.com> Message-ID: <33efb16e0812080639o5c0020b7x6a14a1525a580533@mail.gmail.com> I'm stuck. I posted the below on the Ubuntu Forum and have had 48 reads and no responses. How to modify the "mixer" settings? Need a step x step *Alsa and sound problem 8.04.1* ------------------------------ I was advised the following: Open your mixer (gnome-mixer or another one) and make sure that the recording source is set to the Mic entry. Your problem is a simple mixer settings related problem. When I do $alsamixer it shows master (71) PCM (100) Capture(100) Capture(100) Digital (95) Input SO this appears to be the mic (Just shows "mic") How to set recording source to mic? Thanks Bill Collins On Sun, Dec 7, 2008 at 12:22 PM, Edward Dunagin wrote: > Edward Dunagin-Dunigan > Bozeman, MT 59718 > mobile 406-570-0992 > Land line 406-556-7282 > EKIGA: sip:edunagin at ekiga.net > http://doas.montanalinux.org > > > > On Sun, Dec 7, 2008 at 9:09 AM, Damien Sandras > wrote: > > Le samedi 06 d?cembre 2008 ? 20:00 -0500, Bill Collins a ?crit : > >> I have spent considerable time researching the sound problem to no > >> avail. I now turn > >> to the true experts. I have listed as much as I know to help. If more > >> is needed > >> please advise. Also I'm a beginner at this. > >> tia > >> Bill Collins > >> > >> Dell Inspiron B130 1 gb ram > >> Ubuntu 8.04.1 GNOME ekiga 2.0.12 > >> > >> Sound works perfectly well for movies and music. > >> > >> Logitech Quickcam Pro 9000 > >> > >> Video works perfectly well. No sound. Using default audio input and > >> output but > >> did not get any sound return when speaking into microphone. Did "Test > >> 1 2 3 Ekiga Rocks" Nothing comes back. > >> > > > > Open your mixer (gnome-mixer or another one) and make sure that the > > recording source is set to the Mic entry. Your problem is a simple mixer > > settings related problem. > > -- > > _ Damien Sandras > > That maybe so, BUT which mixer??? I use Linux, particularly > Ubuntu8.10. There are three different mixer settings on my system and > the only one I added was the Gnome-alsamixer. They all seem to effect > the system, so if one is set wrong, then all of it is wrong. > > I am an old Linux user and I think this is the reason for all the > problems with sound, and it might be all the problems with video. So, > my advice is if you have more than one mixer and you probably do, make > sure they are ALL set to the settings that you want, sound and video. > > Peace.....................ed > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dford at ansur.demon.co.uk Mon Dec 8 16:29:31 2008 From: dford at ansur.demon.co.uk (David Ford) Date: Mon, 08 Dec 2008 16:29:31 +0000 Subject: [Ekiga-list] No Sound In-Reply-To: <33efb16e0812080639o5c0020b7x6a14a1525a580533@mail.gmail.com> References: <33efb16e0812061700m274f4fedna635d04fd837e67f@mail.gmail.com> <1228666162.17134.81.camel@scorpion.multitel.be> <2af451740812070922t104958ceh439df6c95b5bacdc@mail.gmail.com> <33efb16e0812080639o5c0020b7x6a14a1525a580533@mail.gmail.com> Message-ID: <493D4B6B.5060407@ansur.demon.co.uk> Hi Bill Bill Collins wrote: > I'm stuck. I posted the below on the Ubuntu Forum and have had 48 > reads and no responses. > How to modify the "mixer" settings? > Need a step x step > > *Alsa and sound problem 8.04.1* > ------------------------------------------------------------------------ > I was advised the following: > > Open your mixer (gnome-mixer or another one) and make sure that the > recording source is set to the Mic entry. Your problem is a simple mixer > settings related problem. > > When I do > $alsamixer Alsamixer is a little difficult to use - type 'man alsamixer' (without the ') at the command line to read about it. Have you got the little speaker icon - usually in the upper right hand corner on Gnome? Double clicking that should bring you up a GUI mixer. Whats in that mixer will depend on your sound card but hopefully you will have some tabs labeled - Play Record Switches Options - select Switches to turn the mic on and Options to select which mic etc. Hope this helps David > > it shows master (71) > PCM (100) > Capture(100) > Capture(100) > Digital (95) > Input SO this appears to be the mic (Just shows "mic") > > How to set recording source to mic? > > Thanks > Bill Collins > > On Sun, Dec 7, 2008 at 12:22 PM, Edward Dunagin > wrote: > > Edward Dunagin-Dunigan > Bozeman, MT 59718 > mobile 406-570-0992 > Land line 406-556-7282 > EKIGA: sip:edunagin at ekiga.net > http://doas.montanalinux.org > > > > On Sun, Dec 7, 2008 at 9:09 AM, Damien Sandras > > wrote: > > Le samedi 06 d?cembre 2008 ? 20:00 -0500, Bill Collins a ?crit : > >> I have spent considerable time researching the sound problem to no > >> avail. I now turn > >> to the true experts. I have listed as much as I know to help. > If more > >> is needed > >> please advise. Also I'm a beginner at this. > >> tia > >> Bill Collins > >> > >> Dell Inspiron B130 1 gb ram > >> Ubuntu 8.04.1 GNOME ekiga 2.0.12 > >> > >> Sound works perfectly well for movies and music. > >> > >> Logitech Quickcam Pro 9000 > >> > >> Video works perfectly well. No sound. Using default audio input and > >> output but > >> did not get any sound return when speaking into microphone. Did > "Test > >> 1 2 3 Ekiga Rocks" Nothing comes back. > >> > > > > Open your mixer (gnome-mixer or another one) and make sure that the > > recording source is set to the Mic entry. Your problem is a > simple mixer > > settings related problem. > > -- > > _ Damien Sandras > > That maybe so, BUT which mixer??? I use Linux, particularly > Ubuntu8.10. There are three different mixer settings on my system and > the only one I added was the Gnome-alsamixer. They all seem to effect > the system, so if one is set wrong, then all of it is wrong. > > I am an old Linux user and I think this is the reason for all the > problems with sound, and it might be all the problems with video. So, > my advice is if you have more than one mixer and you probably do, make > sure they are ALL set to the settings that you want, sound and video. > > Peace.....................ed > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > > > ------------------------------------------------------------------------ > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list From f.vonbock at gmail.com Mon Dec 8 17:39:48 2008 From: f.vonbock at gmail.com (Fedor vonBock) Date: Mon, 8 Dec 2008 20:39:48 +0300 Subject: [Ekiga-list] can't compile ekiga 3.0.1 ubuntu hardy In-Reply-To: <1228718964.31538.0.camel@scorpion.multitel.be> References: <1228718964.31538.0.camel@scorpion.multitel.be> Message-ID: THanks for replying...this is the error that i get when i do "make", i don't know why ======================================================== Now type `make' to compile ekiga khalfan at khalfan-desktop:~/build-hardy/ekiga$ khalfan at khalfan-desktop:~/build-hardy/ekiga$ sudo make make all-recursive make[1]: Entering directory `/home/khalfan/build-hardy/ekiga' Making all in man make[2]: Entering directory `/home/khalfan/build-hardy/ekiga/man' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/home/khalfan/build-hardy/ekiga/man' Making all in sounds make[2]: Entering directory `/home/khalfan/build-hardy/ekiga/sounds' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/home/khalfan/build-hardy/ekiga/sounds' Making all in pixmaps make[2]: Entering directory `/home/khalfan/build-hardy/ekiga/pixmaps' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/home/khalfan/build-hardy/ekiga/pixmaps' Making all in lib make[2]: Entering directory `/home/khalfan/build-hardy/ekiga/lib' make all-recursive make[3]: Entering directory `/home/khalfan/build-hardy/ekiga/lib' Making all in gmconf make[4]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/gmconf' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/gmconf' Making all in gui make[4]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/gui' make[5]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/gui' make[5]: Nothing to be done for `all-am'. make[5]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/gui' make[4]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/gui' Making all in toolbox make[4]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/toolbox' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/toolbox' Making all in platform make[4]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/platform' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/platform' Making all in pixops make[4]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/pixops' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/pixops' Making all in engine make[4]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine' Making all in framework make[5]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/framework' make[5]: Nothing to be done for `all'. make[5]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/framework' Making all in account make[5]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/account' Making all in skel make[6]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/account/skel' make[6]: Nothing to be done for `all'. make[6]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/account/skel' make[6]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/account' make[6]: Nothing to be done for `all-am'. make[6]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/account' make[5]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/account' Making all in addressbook make[5]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/addressbook' Making all in skel make[6]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/addressbook/skel' make[6]: Nothing to be done for `all'. make[6]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/addressbook/skel' make[6]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/addressbook' make[6]: Nothing to be done for `all-am'. make[6]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/addressbook' make[5]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/addressbook' Making all in presence make[5]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/presence' Making all in skel make[6]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/presence/skel' make[6]: Nothing to be done for `all'. make[6]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/presence/skel' make[6]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/presence' make[6]: Nothing to be done for `all-am'. make[6]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/presence' make[5]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/presence' Making all in chat make[5]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/chat' Making all in skel make[6]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/chat/skel' make[6]: Nothing to be done for `all'. make[6]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/chat/skel' Making all in echo make[6]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/chat/echo' make[6]: Nothing to be done for `all'. make[6]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/chat/echo' make[6]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/chat' make[6]: Nothing to be done for `all-am'. make[6]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/chat' make[5]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/chat' Making all in gui make[5]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/gui' Making all in gtk-core make[6]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/gui/gtk-core' make[6]: Nothing to be done for `all'. make[6]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/gui/gtk-core' Making all in gtk-frontend make[6]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/gui/gtk-frontend' make[6]: Nothing to be done for `all'. make[6]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/gui/gtk-frontend' make[6]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/gui' make[6]: Nothing to be done for `all-am'. make[6]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/gui' make[5]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/gui' Making all in protocol make[5]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/protocol' Making all in skel make[6]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/protocol/skel' make[6]: Nothing to be done for `all'. make[6]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/protocol/skel' make[6]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/protocol' make[6]: Nothing to be done for `all-am'. make[6]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/protocol' make[5]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/protocol' Making all in videooutput make[5]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/videooutput' Making all in skel make[6]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/videooutput/skel' make[6]: Nothing to be done for `all'. make[6]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/videooutput/skel' Making all in x make[6]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/videooutput/x' make[6]: Nothing to be done for `all'. make[6]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/videooutput/x' make[6]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/videooutput' make[6]: Nothing to be done for `all-am'. make[6]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/videooutput' make[5]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/videooutput' Making all in videoinput make[5]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/videoinput' Making all in skel make[6]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/videoinput/skel' make[6]: Nothing to be done for `all'. make[6]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/videoinput/skel' Making all in mlogo make[6]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/videoinput/mlogo' make[6]: Nothing to be done for `all'. make[6]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/videoinput/mlogo' make[6]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/videoinput' make[6]: Nothing to be done for `all-am'. make[6]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/videoinput' make[5]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/videoinput' Making all in audioinput make[5]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/audioinput' Making all in skel make[6]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/audioinput/skel' make[6]: Nothing to be done for `all'. make[6]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/audioinput/skel' Making all in null make[6]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/audioinput/null' make[6]: Nothing to be done for `all'. make[6]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/audioinput/null' make[6]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/audioinput' make[6]: Nothing to be done for `all-am'. make[6]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/audioinput' make[5]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/audioinput' Making all in audiooutput make[5]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/audiooutput' Making all in skel make[6]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/audiooutput/skel' make[6]: Nothing to be done for `all'. make[6]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/audiooutput/skel' Making all in null make[6]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/audiooutput/null' make[6]: Nothing to be done for `all'. make[6]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/audiooutput/null' make[6]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/audiooutput' make[6]: Nothing to be done for `all-am'. make[6]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/audiooutput' make[5]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/audiooutput' Making all in hal make[5]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/hal' Making all in skel make[6]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/hal/skel' make[6]: Nothing to be done for `all'. make[6]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/hal/skel' Making all in dbus make[6]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/hal/dbus' make all-am make[7]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/hal/dbus' make[7]: Nothing to be done for `all-am'. make[7]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/hal/dbus' make[6]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/hal/dbus' make[6]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/hal' make[6]: Nothing to be done for `all-am'. make[6]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/hal' make[5]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/hal' Making all in components make[5]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/components' Making all in call-history make[6]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/components/call-history' make[6]: Nothing to be done for `all'. make[6]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/components/call-history' Making all in gmconf-personal-details make[6]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/components/gmconf-personal-details' make[6]: Nothing to be done for `all'. make[6]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/components/gmconf-personal-details' Making all in local-roster make[6]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/components/local-roster' make[6]: Nothing to be done for `all'. make[6]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/components/local-roster' Making all in opal make[6]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/components/opal' make[6]: Nothing to be done for `all'. make[6]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/components/opal' Making all in ptlib make[6]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/components/ptlib' make[6]: Nothing to be done for `all'. make[6]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/components/ptlib' Making all in avahi-publisher make[6]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/components/avahi-publisher' make[6]: Nothing to be done for `all'. make[6]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/components/avahi-publisher' Making all in avahi make[6]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/components/avahi' make[6]: Nothing to be done for `all'. make[6]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/components/avahi' Making all in evolution make[6]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/components/evolution' make[6]: Nothing to be done for `all'. make[6]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/components/evolution' Making all in ldap make[6]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/components/ldap' make[6]: Nothing to be done for `all'. make[6]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/components/ldap' make[6]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/components' make[6]: Nothing to be done for `all-am'. make[6]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/components' make[5]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/components' make[5]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine' make[5]: Nothing to be done for `all-am'. make[5]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine' make[4]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine' make[4]: Entering directory `/home/khalfan/build-hardy/ekiga/lib' make[4]: Nothing to be done for `all-am'. make[4]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib' make[3]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib' make[2]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib' Making all in src make[2]: Entering directory `/home/khalfan/build-hardy/ekiga/src' make all-am make[3]: Entering directory `/home/khalfan/build-hardy/ekiga/src' g++ -DHAVE_CONFIG_H -I. -I.. -I../lib -I../lib/gmconf -I../lib/toolbox -I../lib/gui -I../lib/engine/ -I../lib/engine/framework -I../lib/engine/gui/gtk-frontend -I../lib/engine/account/skel -I../lib/engine/addressbook/skel -I../lib/engine/chat/skel -I../lib/engine/presence/skel -I../lib/engine/protocol/skel -I../lib/engine/protocol/sip -I../lib/engine/videooutput/skel -I../lib/engine/videoinput/skel -I../lib/engine/audioinput/skel -I../lib/engine/audiooutput/skel -I../lib/engine/hal/skel -I../lib/engine/framework -I../lib/engine/gui/gtk-core -I../lib/engine/components/opal -I../src -I../src/dbus-helper/ -I../src/gui/ -I.. -DSCHEMA_AGE=62 -I../lib/engine/videooutput/common -I../lib/engine/videooutput/x -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/pixman-1 -DGDK_PIXBUF_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED -DGTK_DISABLE_DEPRECATED -DGDK_PIXBUF_DISABLE_SINGLE_INCLUDES -DGTK_DISABLE_SINGLE_INCLUDES -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DG_DISABLE_SINGLE_INCLUDES -DORBIT2=1 -pthread -I/usr/include/libgnome-2.0 -I/usr/include/orbit-2.0 -I/usr/include/gconf/2 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libgnomeui-2.0 -I/usr/include/libart-2.0 -I/usr/include/gnome-keyring-1 -I/usr/include/libbonoboui-2.0 -I/usr/include/libgnomecanvas-2.0 -I/usr/include/gtk-2.0 -I/usr/include/libxml2 -I/usr/include/pango-1.0 -I/usr/include/gail-1.0 -I/usr/include/freetype2 -I/usr/include/atk-1.0 -I/usr/lib/gtk-2.0/include -I/usr/include/cairo -I/usr/include/libpng12 -I/usr/include/pixman-1 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DPTRACING=1 -D_REENTRANT -fno-exceptions -I/usr/include/opal -DPTRACING=1 -D_REENTRANT -fno-exceptions -I/usr/include/sigc++-2.0 -I/usr/lib/sigc++-2.0/include -I/usr/include/libxml2 -g -O2 -Wall -Wextra -Winit-self -Wswitch-default -Wswitch-enum -Wstrict-aliasing=2 -Wfloat-equal -Wshadow -MT main.o -MD -MP -MF .deps/main.Tpo -c -o main.o `test -f 'gui/main.cpp' || echo './'`gui/main.cpp gui/main.cpp: In function 'int main(int, char**, char**)': gui/main.cpp:4350: error: cannot call member function 'void PProcess::PreInitialise(int, char**, char**)' without object make[3]: *** [main.o] Error 1 make[3]: Leaving directory `/home/khalfan/build-hardy/ekiga/src' make[2]: *** [all] Error 2 make[2]: Leaving directory `/home/khalfan/build-hardy/ekiga/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/khalfan/build-hardy/ekiga' make: *** [all] Error 2 On 12/8/08, Damien Sandras wrote: > Le dimanche 07 d?cembre 2008 ? 22:09 +0300, Fedor vonBock a ?crit : >> Hi, >> >> I used this site >> (http://wiki.ekiga.org/index.php/Talk:Additional_Information#PTLIB) to >> help compile and install ekiga 3.0.1. However, i notice a difference >> in the final configuration where the directories for the PTLIB and the >> OPAL do not show. I've included my output below and it clearly >> doesn't show the PTLIB and OPAL directories. >> >> >> I tried to compile ekiga later on with make and i got an error >> >> >> >> >> >> ================ Final configuration =================== >> Installing into prefix : /usr >> >> GNOME support : enabled >> GConf support : enabled >> Evolution-Data-Server support : enabled >> NOTIFY support : disabled >> LDAP support : enabled >> >> XVideo support : enabled >> >> H.323 support : yes >> SIP support : yes >> >> DBUS support : enabled >> DBUS service support : enabled >> mDNS/DNS-SD support : enabled >> GStreamer support : disabled >> KAddressBook support : disabled >> KDE support : disabled >> XCAP support : disabled >> >> OS Type : linux-gnu >> Machine Type : i686 >> Byte Order : little endian > > > Where do you see an error ? > -- > _ Damien Sandras > (o- > //\ Ekiga Softphone : http://www.ekiga.org/ > v_/_ Be IP : http://www.beip.be/ > FOSDEM : http://www.fosdem.org/ > SIP Phone : sip:dsandras at ekiga.net > > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list From jbwells at blueyonder.co.uk Mon Dec 8 18:02:21 2008 From: jbwells at blueyonder.co.uk (Joe Wells) Date: Mon, 08 Dec 2008 18:02:21 +0000 Subject: [Ekiga-list] how to bypass SIP server and call a computer directly? Message-ID: <864p1emtoy.fsf@blueyonder.co.uk> Dear Ekiga gurus, How do I bypass a SIP server and call a computer directly? The documentation only describes how to call someone who has an SIP address. However, if I know their IP address, I should be able to contact them directly, right? What do I put as the address to call? Do I just use the raw IP address? Do I need to prefix it by some string? -- Thanks, Joe From michel.memeteau at gmail.com Mon Dec 8 18:15:27 2008 From: michel.memeteau at gmail.com (michel memeteau) Date: Mon, 8 Dec 2008 19:15:27 +0100 Subject: [Ekiga-list] how to bypass SIP server and call a computer directly? In-Reply-To: <864p1emtoy.fsf@blueyonder.co.uk> References: <864p1emtoy.fsf@blueyonder.co.uk> Message-ID: I think putting Whatever at Ipadress will work. On Mon, Dec 8, 2008 at 7:02 PM, Joe Wells wrote: > Dear Ekiga gurus, > > How do I bypass a SIP server and call a computer directly? The > documentation only describes how to call someone who has an SIP > address. However, if I know their IP address, I should be able to > contact them directly, right? What do I put as the address to call? > Do I just use the raw IP address? Do I need to prefix it by some > string? > > -- > Thanks, > > Joe > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > -- %<------------------------------------------------------->% Michel memeteau Blog 0.2 : http://memeteau.free.fr Fixe : 0974763294 Mobile : 0624808051 VOIP | Visio: sip:freechelmi at ippi.fr jabber/GTalk : xmpp:freechelmi at jabber.fr -------------- next part -------------- An HTML attachment was scrubbed... URL: From jbwells at blueyonder.co.uk Mon Dec 8 21:34:21 2008 From: jbwells at blueyonder.co.uk (Joe Wells) Date: Mon, 08 Dec 2008 21:34:21 +0000 Subject: [Ekiga-list] how to bypass SIP server and call a computer directly? In-Reply-To: (michel memeteau's message of "Mon\, 8 Dec 2008 19\:15\:27 +0100") References: <864p1emtoy.fsf@blueyonder.co.uk> Message-ID: <86vdtul5b6.fsf@blueyonder.co.uk> "michel memeteau" writes: > I think putting Whatever at Ipadress will work. Thanks for this information! Testing seems to indicate that XYZ at IPADDRESS, IPADDRESS, sip:XYZ at IPADDRESS, and sip:IPADDRESS all seem to work similarly. What is the rule here? It seems that the ?sip:? prefix is the default and can be omitted. What is used for the part to the left of the ?@? when it is omitted? -- Thanks, Joe > On Mon, Dec 8, 2008 at 7:02 PM, Joe Wells wrote: > > Dear Ekiga gurus, > > How do I bypass a SIP server and call a computer directly? The > documentation only describes how to call someone who has an SIP > address. However, if I know their IP address, I should be able to > contact them directly, right? What do I put as the address to call? > Do I just use the raw IP address? Do I need to prefix it by some > string? > > -- > Thanks, > > Joe From ML at Bartschnet.de Tue Dec 9 01:05:30 2008 From: ML at Bartschnet.de (Rene Bartsch) Date: Tue, 9 Dec 2008 02:05:30 +0100 (CET) Subject: [Ekiga-list] how to bypass SIP server and call a computer directly? In-Reply-To: <86vdtul5b6.fsf@blueyonder.co.uk> References: <864p1emtoy.fsf@blueyonder.co.uk> <86vdtul5b6.fsf@blueyonder.co.uk> Message-ID: <9b7373816d605022ce585a5e783403dd.squirrel@www.bartschnet.de> > "michel memeteau" writes: > >> I think putting Whatever at Ipadress will work. > > Thanks for this information! > > Testing seems to indicate that XYZ at IPADDRESS, IPADDRESS, > sip:XYZ at IPADDRESS, and sip:IPADDRESS all seem to work similarly. > > What is the rule here? It seems that the ???sip:??? prefix is the default > and can be omitted. What is used for the part to the left of the ???@??? > when it is omitted? Depends on the receiver. The syntax is @:. When using standard ports, you don't need (defaults to 5060). is either domain or IP. Some soft- and especially hardphones demand for a while others don't. The AVM Fritzbox is much more special as it only calls callees with a SRV record. But often only works. But there's one special case in Ekiga. Alphanumeric addresses are interpreted as "sip:" while numeric-only addresses are interpreted as ENUM addresses. Renne From jbwells at blueyonder.co.uk Tue Dec 9 08:09:31 2008 From: jbwells at blueyonder.co.uk (Joe Wells) Date: Tue, 09 Dec 2008 08:09:31 +0000 Subject: [Ekiga-list] how to bypass SIP server and call a computer directly? In-Reply-To: <9b7373816d605022ce585a5e783403dd.squirrel@www.bartschnet.de> (Rene Bartsch's message of "Tue\, 9 Dec 2008 02\:05\:30 +0100 \(CET\)") References: <864p1emtoy.fsf@blueyonder.co.uk> <86vdtul5b6.fsf@blueyonder.co.uk> <9b7373816d605022ce585a5e783403dd.squirrel@www.bartschnet.de> Message-ID: <86ej0hlqh0.fsf@blueyonder.co.uk> "Rene Bartsch" writes: >> "michel memeteau" writes: >> >>> I think putting Whatever at Ipadress will work. >> >> Thanks for this information! >> >> Testing seems to indicate that XYZ at IPADDRESS, IPADDRESS, >> sip:XYZ at IPADDRESS, and sip:IPADDRESS all seem to work similarly. >> >> What is the rule here? It seems that the ?sip:? prefix is the >> default and can be omitted. What is used for the part to the left >> of the ?@? when it is omitted? > > Depends on the receiver. The syntax is @:. When > using standard ports, you don't need (defaults to > 5060). is either domain or IP. Some soft- and especially > hardphones demand for a while others don't. What does Ekiga do with a user name on an incoming call? Just ignore it? What happens in general when the user name is left out? > The AVM Fritzboxd is much more special as it only calls callees with > a SRV record. But often only works. > > But there's one special case in Ekiga. Alphanumeric addresses are > interpreted as "sip:" while numeric-only addresses are interpreted > as ENUM addresses. Thanks for this info! Does this mean that ?1234? is equivalent to ?enum:1234?? Is there some standard prefix like ?enum:? that is used for ENUM addresses? -- Joe From dsandras at seconix.com Tue Dec 9 08:41:24 2008 From: dsandras at seconix.com (Damien Sandras) Date: Tue, 09 Dec 2008 09:41:24 +0100 Subject: [Ekiga-list] can't compile ekiga 3.0.1 ubuntu hardy In-Reply-To: References: <1228718964.31538.0.camel@scorpion.multitel.be> Message-ID: <1228812084.31538.32.camel@scorpion.multitel.be> Le lundi 08 d?cembre 2008 ? 20:39 +0300, Fedor vonBock a ?crit : > THanks for replying...this is the error that i get when i do "make", i > don't know why > > > ======================================================== > Now type `make' to compile ekiga > khalfan at khalfan-desktop:~/build-hardy/ekiga$ > khalfan at khalfan-desktop:~/build-hardy/ekiga$ sudo make > make all-recursive > make[1]: Entering directory `/home/khalfan/build-hardy/ekiga' > Making all in man > make[2]: Entering directory `/home/khalfan/build-hardy/ekiga/man' > make[2]: Nothing to be done for `all'. > make[2]: Leaving directory `/home/khalfan/build-hardy/ekiga/man' > Making all in sounds > make[2]: Entering directory `/home/khalfan/build-hardy/ekiga/sounds' > make[2]: Nothing to be done for `all'. > make[2]: Leaving directory `/home/khalfan/build-hardy/ekiga/sounds' > Making all in pixmaps > make[2]: Entering directory `/home/khalfan/build-hardy/ekiga/pixmaps' > make[2]: Nothing to be done for `all'. > make[2]: Leaving directory `/home/khalfan/build-hardy/ekiga/pixmaps' > Making all in lib > make[2]: Entering directory `/home/khalfan/build-hardy/ekiga/lib' > make all-recursive > make[3]: Entering directory `/home/khalfan/build-hardy/ekiga/lib' > Making all in gmconf > make[4]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/gmconf' > make[4]: Nothing to be done for `all'. > make[4]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/gmconf' > Making all in gui > make[4]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/gui' > make[5]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/gui' > make[5]: Nothing to be done for `all-am'. > make[5]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/gui' > make[4]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/gui' > Making all in toolbox > make[4]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/toolbox' > make[4]: Nothing to be done for `all'. > make[4]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/toolbox' > Making all in platform > make[4]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/platform' > make[4]: Nothing to be done for `all'. > make[4]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/platform' > Making all in pixops > make[4]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/pixops' > make[4]: Nothing to be done for `all'. > make[4]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/pixops' > Making all in engine > make[4]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine' > Making all in framework > make[5]: Entering directory > `/home/khalfan/build-hardy/ekiga/lib/engine/framework' > make[5]: Nothing to be done for `all'. > make[5]: Leaving directory > `/home/khalfan/build-hardy/ekiga/lib/engine/framework' > Making all in account > make[5]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/account' > Making all in skel > make[6]: Entering directory > `/home/khalfan/build-hardy/ekiga/lib/engine/account/skel' > make[6]: Nothing to be done for `all'. > make[6]: Leaving directory > `/home/khalfan/build-hardy/ekiga/lib/engine/account/skel' > make[6]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/account' > make[6]: Nothing to be done for `all-am'. > make[6]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/account' > make[5]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/account' > Making all in addressbook > make[5]: Entering directory > `/home/khalfan/build-hardy/ekiga/lib/engine/addressbook' > Making all in skel > make[6]: Entering directory > `/home/khalfan/build-hardy/ekiga/lib/engine/addressbook/skel' > make[6]: Nothing to be done for `all'. > make[6]: Leaving directory > `/home/khalfan/build-hardy/ekiga/lib/engine/addressbook/skel' > make[6]: Entering directory > `/home/khalfan/build-hardy/ekiga/lib/engine/addressbook' > make[6]: Nothing to be done for `all-am'. > make[6]: Leaving directory > `/home/khalfan/build-hardy/ekiga/lib/engine/addressbook' > make[5]: Leaving directory > `/home/khalfan/build-hardy/ekiga/lib/engine/addressbook' > Making all in presence > make[5]: Entering directory > `/home/khalfan/build-hardy/ekiga/lib/engine/presence' > Making all in skel > make[6]: Entering directory > `/home/khalfan/build-hardy/ekiga/lib/engine/presence/skel' > make[6]: Nothing to be done for `all'. > make[6]: Leaving directory > `/home/khalfan/build-hardy/ekiga/lib/engine/presence/skel' > make[6]: Entering directory > `/home/khalfan/build-hardy/ekiga/lib/engine/presence' > make[6]: Nothing to be done for `all-am'. > make[6]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/presence' > make[5]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/presence' > Making all in chat > make[5]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/chat' > Making all in skel > make[6]: Entering directory > `/home/khalfan/build-hardy/ekiga/lib/engine/chat/skel' > make[6]: Nothing to be done for `all'. > make[6]: Leaving directory > `/home/khalfan/build-hardy/ekiga/lib/engine/chat/skel' > Making all in echo > make[6]: Entering directory > `/home/khalfan/build-hardy/ekiga/lib/engine/chat/echo' > make[6]: Nothing to be done for `all'. > make[6]: Leaving directory > `/home/khalfan/build-hardy/ekiga/lib/engine/chat/echo' > make[6]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/chat' > make[6]: Nothing to be done for `all-am'. > make[6]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/chat' > make[5]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/chat' > Making all in gui > make[5]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/gui' > Making all in gtk-core > make[6]: Entering directory > `/home/khalfan/build-hardy/ekiga/lib/engine/gui/gtk-core' > make[6]: Nothing to be done for `all'. > make[6]: Leaving directory > `/home/khalfan/build-hardy/ekiga/lib/engine/gui/gtk-core' > Making all in gtk-frontend > make[6]: Entering directory > `/home/khalfan/build-hardy/ekiga/lib/engine/gui/gtk-frontend' > make[6]: Nothing to be done for `all'. > make[6]: Leaving directory > `/home/khalfan/build-hardy/ekiga/lib/engine/gui/gtk-frontend' > make[6]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/gui' > make[6]: Nothing to be done for `all-am'. > make[6]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/gui' > make[5]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/gui' > Making all in protocol > make[5]: Entering directory > `/home/khalfan/build-hardy/ekiga/lib/engine/protocol' > Making all in skel > make[6]: Entering directory > `/home/khalfan/build-hardy/ekiga/lib/engine/protocol/skel' > make[6]: Nothing to be done for `all'. > make[6]: Leaving directory > `/home/khalfan/build-hardy/ekiga/lib/engine/protocol/skel' > make[6]: Entering directory > `/home/khalfan/build-hardy/ekiga/lib/engine/protocol' > make[6]: Nothing to be done for `all-am'. > make[6]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/protocol' > make[5]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/protocol' > Making all in videooutput > make[5]: Entering directory > `/home/khalfan/build-hardy/ekiga/lib/engine/videooutput' > Making all in skel > make[6]: Entering directory > `/home/khalfan/build-hardy/ekiga/lib/engine/videooutput/skel' > make[6]: Nothing to be done for `all'. > make[6]: Leaving directory > `/home/khalfan/build-hardy/ekiga/lib/engine/videooutput/skel' > Making all in x > make[6]: Entering directory > `/home/khalfan/build-hardy/ekiga/lib/engine/videooutput/x' > make[6]: Nothing to be done for `all'. > make[6]: Leaving directory > `/home/khalfan/build-hardy/ekiga/lib/engine/videooutput/x' > make[6]: Entering directory > `/home/khalfan/build-hardy/ekiga/lib/engine/videooutput' > make[6]: Nothing to be done for `all-am'. > make[6]: Leaving directory > `/home/khalfan/build-hardy/ekiga/lib/engine/videooutput' > make[5]: Leaving directory > `/home/khalfan/build-hardy/ekiga/lib/engine/videooutput' > Making all in videoinput > make[5]: Entering directory > `/home/khalfan/build-hardy/ekiga/lib/engine/videoinput' > Making all in skel > make[6]: Entering directory > `/home/khalfan/build-hardy/ekiga/lib/engine/videoinput/skel' > make[6]: Nothing to be done for `all'. > make[6]: Leaving directory > `/home/khalfan/build-hardy/ekiga/lib/engine/videoinput/skel' > Making all in mlogo > make[6]: Entering directory > `/home/khalfan/build-hardy/ekiga/lib/engine/videoinput/mlogo' > make[6]: Nothing to be done for `all'. > make[6]: Leaving directory > `/home/khalfan/build-hardy/ekiga/lib/engine/videoinput/mlogo' > make[6]: Entering directory > `/home/khalfan/build-hardy/ekiga/lib/engine/videoinput' > make[6]: Nothing to be done for `all-am'. > make[6]: Leaving directory > `/home/khalfan/build-hardy/ekiga/lib/engine/videoinput' > make[5]: Leaving directory > `/home/khalfan/build-hardy/ekiga/lib/engine/videoinput' > Making all in audioinput > make[5]: Entering directory > `/home/khalfan/build-hardy/ekiga/lib/engine/audioinput' > Making all in skel > make[6]: Entering directory > `/home/khalfan/build-hardy/ekiga/lib/engine/audioinput/skel' > make[6]: Nothing to be done for `all'. > make[6]: Leaving directory > `/home/khalfan/build-hardy/ekiga/lib/engine/audioinput/skel' > Making all in null > make[6]: Entering directory > `/home/khalfan/build-hardy/ekiga/lib/engine/audioinput/null' > make[6]: Nothing to be done for `all'. > make[6]: Leaving directory > `/home/khalfan/build-hardy/ekiga/lib/engine/audioinput/null' > make[6]: Entering directory > `/home/khalfan/build-hardy/ekiga/lib/engine/audioinput' > make[6]: Nothing to be done for `all-am'. > make[6]: Leaving directory > `/home/khalfan/build-hardy/ekiga/lib/engine/audioinput' > make[5]: Leaving directory > `/home/khalfan/build-hardy/ekiga/lib/engine/audioinput' > Making all in audiooutput > make[5]: Entering directory > `/home/khalfan/build-hardy/ekiga/lib/engine/audiooutput' > Making all in skel > make[6]: Entering directory > `/home/khalfan/build-hardy/ekiga/lib/engine/audiooutput/skel' > make[6]: Nothing to be done for `all'. > make[6]: Leaving directory > `/home/khalfan/build-hardy/ekiga/lib/engine/audiooutput/skel' > Making all in null > make[6]: Entering directory > `/home/khalfan/build-hardy/ekiga/lib/engine/audiooutput/null' > make[6]: Nothing to be done for `all'. > make[6]: Leaving directory > `/home/khalfan/build-hardy/ekiga/lib/engine/audiooutput/null' > make[6]: Entering directory > `/home/khalfan/build-hardy/ekiga/lib/engine/audiooutput' > make[6]: Nothing to be done for `all-am'. > make[6]: Leaving directory > `/home/khalfan/build-hardy/ekiga/lib/engine/audiooutput' > make[5]: Leaving directory > `/home/khalfan/build-hardy/ekiga/lib/engine/audiooutput' > Making all in hal > make[5]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/hal' > Making all in skel > make[6]: Entering directory > `/home/khalfan/build-hardy/ekiga/lib/engine/hal/skel' > make[6]: Nothing to be done for `all'. > make[6]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/hal/skel' > Making all in dbus > make[6]: Entering directory > `/home/khalfan/build-hardy/ekiga/lib/engine/hal/dbus' > make all-am > make[7]: Entering directory > `/home/khalfan/build-hardy/ekiga/lib/engine/hal/dbus' > make[7]: Nothing to be done for `all-am'. > make[7]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/hal/dbus' > make[6]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/hal/dbus' > make[6]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/hal' > make[6]: Nothing to be done for `all-am'. > make[6]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/hal' > make[5]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/hal' > Making all in components > make[5]: Entering directory > `/home/khalfan/build-hardy/ekiga/lib/engine/components' > Making all in call-history > make[6]: Entering directory > `/home/khalfan/build-hardy/ekiga/lib/engine/components/call-history' > make[6]: Nothing to be done for `all'. > make[6]: Leaving directory > `/home/khalfan/build-hardy/ekiga/lib/engine/components/call-history' > Making all in gmconf-personal-details > make[6]: Entering directory > `/home/khalfan/build-hardy/ekiga/lib/engine/components/gmconf-personal-details' > make[6]: Nothing to be done for `all'. > make[6]: Leaving directory > `/home/khalfan/build-hardy/ekiga/lib/engine/components/gmconf-personal-details' > Making all in local-roster > make[6]: Entering directory > `/home/khalfan/build-hardy/ekiga/lib/engine/components/local-roster' > make[6]: Nothing to be done for `all'. > make[6]: Leaving directory > `/home/khalfan/build-hardy/ekiga/lib/engine/components/local-roster' > Making all in opal > make[6]: Entering directory > `/home/khalfan/build-hardy/ekiga/lib/engine/components/opal' > make[6]: Nothing to be done for `all'. > make[6]: Leaving directory > `/home/khalfan/build-hardy/ekiga/lib/engine/components/opal' > Making all in ptlib > make[6]: Entering directory > `/home/khalfan/build-hardy/ekiga/lib/engine/components/ptlib' > make[6]: Nothing to be done for `all'. > make[6]: Leaving directory > `/home/khalfan/build-hardy/ekiga/lib/engine/components/ptlib' > Making all in avahi-publisher > make[6]: Entering directory > `/home/khalfan/build-hardy/ekiga/lib/engine/components/avahi-publisher' > make[6]: Nothing to be done for `all'. > make[6]: Leaving directory > `/home/khalfan/build-hardy/ekiga/lib/engine/components/avahi-publisher' > Making all in avahi > make[6]: Entering directory > `/home/khalfan/build-hardy/ekiga/lib/engine/components/avahi' > make[6]: Nothing to be done for `all'. > make[6]: Leaving directory > `/home/khalfan/build-hardy/ekiga/lib/engine/components/avahi' > Making all in evolution > make[6]: Entering directory > `/home/khalfan/build-hardy/ekiga/lib/engine/components/evolution' > make[6]: Nothing to be done for `all'. > make[6]: Leaving directory > `/home/khalfan/build-hardy/ekiga/lib/engine/components/evolution' > Making all in ldap > make[6]: Entering directory > `/home/khalfan/build-hardy/ekiga/lib/engine/components/ldap' > make[6]: Nothing to be done for `all'. > make[6]: Leaving directory > `/home/khalfan/build-hardy/ekiga/lib/engine/components/ldap' > make[6]: Entering directory > `/home/khalfan/build-hardy/ekiga/lib/engine/components' > make[6]: Nothing to be done for `all-am'. > make[6]: Leaving directory > `/home/khalfan/build-hardy/ekiga/lib/engine/components' > make[5]: Leaving directory > `/home/khalfan/build-hardy/ekiga/lib/engine/components' > make[5]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine' > make[5]: Nothing to be done for `all-am'. > make[5]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine' > make[4]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine' > make[4]: Entering directory `/home/khalfan/build-hardy/ekiga/lib' > make[4]: Nothing to be done for `all-am'. > make[4]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib' > make[3]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib' > make[2]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib' > Making all in src > make[2]: Entering directory `/home/khalfan/build-hardy/ekiga/src' > make all-am > make[3]: Entering directory `/home/khalfan/build-hardy/ekiga/src' > g++ -DHAVE_CONFIG_H -I. -I.. -I../lib -I../lib/gmconf -I../lib/toolbox > -I../lib/gui -I../lib/engine/ -I../lib/engine/framework > -I../lib/engine/gui/gtk-frontend -I../lib/engine/account/skel > -I../lib/engine/addressbook/skel -I../lib/engine/chat/skel > -I../lib/engine/presence/skel -I../lib/engine/protocol/skel > -I../lib/engine/protocol/sip -I../lib/engine/videooutput/skel > -I../lib/engine/videoinput/skel -I../lib/engine/audioinput/skel > -I../lib/engine/audiooutput/skel -I../lib/engine/hal/skel > -I../lib/engine/framework -I../lib/engine/gui/gtk-core > -I../lib/engine/components/opal -I../src -I../src/dbus-helper/ > -I../src/gui/ -I.. -DSCHEMA_AGE=62 -I../lib/engine/videooutput/common > -I../lib/engine/videooutput/x -I/usr/include/gtk-2.0 > -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo > -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 > -I/usr/lib/glib-2.0/include -I/usr/include/freetype2 > -I/usr/include/libpng12 -I/usr/include/pixman-1 > -DGDK_PIXBUF_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED > -DGTK_DISABLE_DEPRECATED -DGDK_PIXBUF_DISABLE_SINGLE_INCLUDES > -DGTK_DISABLE_SINGLE_INCLUDES -pthread -I/usr/include/glib-2.0 > -I/usr/lib/glib-2.0/include -DG_DISABLE_SINGLE_INCLUDES -DORBIT2=1 > -pthread -I/usr/include/libgnome-2.0 -I/usr/include/orbit-2.0 > -I/usr/include/gconf/2 -I/usr/include/gnome-vfs-2.0 > -I/usr/lib/gnome-vfs-2.0/include -I/usr/include/glib-2.0 > -I/usr/lib/glib-2.0/include -I/usr/include/libbonobo-2.0 > -I/usr/include/bonobo-activation-2.0 -I/usr/include/libgnomeui-2.0 > -I/usr/include/libart-2.0 -I/usr/include/gnome-keyring-1 > -I/usr/include/libbonoboui-2.0 -I/usr/include/libgnomecanvas-2.0 > -I/usr/include/gtk-2.0 -I/usr/include/libxml2 -I/usr/include/pango-1.0 > -I/usr/include/gail-1.0 -I/usr/include/freetype2 > -I/usr/include/atk-1.0 -I/usr/lib/gtk-2.0/include -I/usr/include/cairo > -I/usr/include/libpng12 -I/usr/include/pixman-1 > -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include > -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DPTRACING=1 > -D_REENTRANT -fno-exceptions -I/usr/include/opal -DPTRACING=1 > -D_REENTRANT -fno-exceptions -I/usr/include/sigc++-2.0 > -I/usr/lib/sigc++-2.0/include -I/usr/include/libxml2 -g -O2 -Wall > -Wextra -Winit-self -Wswitch-default -Wswitch-enum -Wstrict-aliasing=2 > -Wfloat-equal -Wshadow -MT main.o -MD -MP -MF .deps/main.Tpo -c -o > main.o `test -f 'gui/main.cpp' || echo './'`gui/main.cpp > gui/main.cpp: In function 'int main(int, char**, char**)': > gui/main.cpp:4350: error: cannot call member function 'void > PProcess::PreInitialise(int, char**, char**)' without object > make[3]: *** [main.o] Error 1 > make[3]: Leaving directory `/home/khalfan/build-hardy/ekiga/src' > make[2]: *** [all] Error 2 > make[2]: Leaving directory `/home/khalfan/build-hardy/ekiga/src' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/home/khalfan/build-hardy/ekiga' > make: *** [all] Error 2 You are compiling ekiga 3.0.1 with OPAL and PTLIB TRUNK. Either use the stable releases for all of them, or the TRUNK releases for all of them, but don't mix them together. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From f.vonbock at gmail.com Tue Dec 9 15:24:45 2008 From: f.vonbock at gmail.com (Ali) Date: Tue, 09 Dec 2008 18:24:45 +0300 Subject: [Ekiga-list] can't compile ekiga 3.0.1 ubuntu hardy In-Reply-To: <1228812084.31538.32.camel@scorpion.multitel.be> References: <1228718964.31538.0.camel@scorpion.multitel.be> <1228812084.31538.32.camel@scorpion.multitel.be> Message-ID: <493E8DBD.4060204@gmail.com> Damien Sandras wrote: > Le lundi 08 d?cembre 2008 ? 20:39 +0300, Fedor vonBock a ?crit : > >> THanks for replying...this is the error that i get when i do "make", i >> don't know why >> >> >> ======================================================== >> Now type `make' to compile ekiga >> khalfan at khalfan-desktop:~/build-hardy/ekiga$ >> khalfan at khalfan-desktop:~/build-hardy/ekiga$ sudo make >> make all-recursive >> make[1]: Entering directory `/home/khalfan/build-hardy/ekiga' >> Making all in man >> make[2]: Entering directory `/home/khalfan/build-hardy/ekiga/man' >> make[2]: Nothing to be done for `all'. >> make[2]: Leaving directory `/home/khalfan/build-hardy/ekiga/man' >> Making all in sounds >> make[2]: Entering directory `/home/khalfan/build-hardy/ekiga/sounds' >> make[2]: Nothing to be done for `all'. >> make[2]: Leaving directory `/home/khalfan/build-hardy/ekiga/sounds' >> Making all in pixmaps >> make[2]: Entering directory `/home/khalfan/build-hardy/ekiga/pixmaps' >> make[2]: Nothing to be done for `all'. >> make[2]: Leaving directory `/home/khalfan/build-hardy/ekiga/pixmaps' >> Making all in lib >> make[2]: Entering directory `/home/khalfan/build-hardy/ekiga/lib' >> make all-recursive >> make[3]: Entering directory `/home/khalfan/build-hardy/ekiga/lib' >> Making all in gmconf >> make[4]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/gmconf' >> make[4]: Nothing to be done for `all'. >> make[4]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/gmconf' >> Making all in gui >> make[4]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/gui' >> make[5]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/gui' >> make[5]: Nothing to be done for `all-am'. >> make[5]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/gui' >> make[4]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/gui' >> Making all in toolbox >> make[4]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/toolbox' >> make[4]: Nothing to be done for `all'. >> make[4]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/toolbox' >> Making all in platform >> make[4]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/platform' >> make[4]: Nothing to be done for `all'. >> make[4]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/platform' >> Making all in pixops >> make[4]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/pixops' >> make[4]: Nothing to be done for `all'. >> make[4]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/pixops' >> Making all in engine >> make[4]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine' >> Making all in framework >> make[5]: Entering directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/framework' >> make[5]: Nothing to be done for `all'. >> make[5]: Leaving directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/framework' >> Making all in account >> make[5]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/account' >> Making all in skel >> make[6]: Entering directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/account/skel' >> make[6]: Nothing to be done for `all'. >> make[6]: Leaving directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/account/skel' >> make[6]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/account' >> make[6]: Nothing to be done for `all-am'. >> make[6]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/account' >> make[5]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/account' >> Making all in addressbook >> make[5]: Entering directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/addressbook' >> Making all in skel >> make[6]: Entering directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/addressbook/skel' >> make[6]: Nothing to be done for `all'. >> make[6]: Leaving directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/addressbook/skel' >> make[6]: Entering directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/addressbook' >> make[6]: Nothing to be done for `all-am'. >> make[6]: Leaving directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/addressbook' >> make[5]: Leaving directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/addressbook' >> Making all in presence >> make[5]: Entering directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/presence' >> Making all in skel >> make[6]: Entering directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/presence/skel' >> make[6]: Nothing to be done for `all'. >> make[6]: Leaving directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/presence/skel' >> make[6]: Entering directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/presence' >> make[6]: Nothing to be done for `all-am'. >> make[6]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/presence' >> make[5]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/presence' >> Making all in chat >> make[5]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/chat' >> Making all in skel >> make[6]: Entering directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/chat/skel' >> make[6]: Nothing to be done for `all'. >> make[6]: Leaving directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/chat/skel' >> Making all in echo >> make[6]: Entering directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/chat/echo' >> make[6]: Nothing to be done for `all'. >> make[6]: Leaving directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/chat/echo' >> make[6]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/chat' >> make[6]: Nothing to be done for `all-am'. >> make[6]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/chat' >> make[5]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/chat' >> Making all in gui >> make[5]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/gui' >> Making all in gtk-core >> make[6]: Entering directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/gui/gtk-core' >> make[6]: Nothing to be done for `all'. >> make[6]: Leaving directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/gui/gtk-core' >> Making all in gtk-frontend >> make[6]: Entering directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/gui/gtk-frontend' >> make[6]: Nothing to be done for `all'. >> make[6]: Leaving directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/gui/gtk-frontend' >> make[6]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/gui' >> make[6]: Nothing to be done for `all-am'. >> make[6]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/gui' >> make[5]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/gui' >> Making all in protocol >> make[5]: Entering directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/protocol' >> Making all in skel >> make[6]: Entering directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/protocol/skel' >> make[6]: Nothing to be done for `all'. >> make[6]: Leaving directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/protocol/skel' >> make[6]: Entering directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/protocol' >> make[6]: Nothing to be done for `all-am'. >> make[6]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/protocol' >> make[5]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/protocol' >> Making all in videooutput >> make[5]: Entering directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/videooutput' >> Making all in skel >> make[6]: Entering directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/videooutput/skel' >> make[6]: Nothing to be done for `all'. >> make[6]: Leaving directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/videooutput/skel' >> Making all in x >> make[6]: Entering directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/videooutput/x' >> make[6]: Nothing to be done for `all'. >> make[6]: Leaving directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/videooutput/x' >> make[6]: Entering directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/videooutput' >> make[6]: Nothing to be done for `all-am'. >> make[6]: Leaving directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/videooutput' >> make[5]: Leaving directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/videooutput' >> Making all in videoinput >> make[5]: Entering directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/videoinput' >> Making all in skel >> make[6]: Entering directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/videoinput/skel' >> make[6]: Nothing to be done for `all'. >> make[6]: Leaving directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/videoinput/skel' >> Making all in mlogo >> make[6]: Entering directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/videoinput/mlogo' >> make[6]: Nothing to be done for `all'. >> make[6]: Leaving directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/videoinput/mlogo' >> make[6]: Entering directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/videoinput' >> make[6]: Nothing to be done for `all-am'. >> make[6]: Leaving directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/videoinput' >> make[5]: Leaving directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/videoinput' >> Making all in audioinput >> make[5]: Entering directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/audioinput' >> Making all in skel >> make[6]: Entering directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/audioinput/skel' >> make[6]: Nothing to be done for `all'. >> make[6]: Leaving directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/audioinput/skel' >> Making all in null >> make[6]: Entering directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/audioinput/null' >> make[6]: Nothing to be done for `all'. >> make[6]: Leaving directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/audioinput/null' >> make[6]: Entering directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/audioinput' >> make[6]: Nothing to be done for `all-am'. >> make[6]: Leaving directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/audioinput' >> make[5]: Leaving directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/audioinput' >> Making all in audiooutput >> make[5]: Entering directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/audiooutput' >> Making all in skel >> make[6]: Entering directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/audiooutput/skel' >> make[6]: Nothing to be done for `all'. >> make[6]: Leaving directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/audiooutput/skel' >> Making all in null >> make[6]: Entering directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/audiooutput/null' >> make[6]: Nothing to be done for `all'. >> make[6]: Leaving directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/audiooutput/null' >> make[6]: Entering directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/audiooutput' >> make[6]: Nothing to be done for `all-am'. >> make[6]: Leaving directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/audiooutput' >> make[5]: Leaving directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/audiooutput' >> Making all in hal >> make[5]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/hal' >> Making all in skel >> make[6]: Entering directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/hal/skel' >> make[6]: Nothing to be done for `all'. >> make[6]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/hal/skel' >> Making all in dbus >> make[6]: Entering directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/hal/dbus' >> make all-am >> make[7]: Entering directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/hal/dbus' >> make[7]: Nothing to be done for `all-am'. >> make[7]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/hal/dbus' >> make[6]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/hal/dbus' >> make[6]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine/hal' >> make[6]: Nothing to be done for `all-am'. >> make[6]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/hal' >> make[5]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine/hal' >> Making all in components >> make[5]: Entering directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/components' >> Making all in call-history >> make[6]: Entering directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/components/call-history' >> make[6]: Nothing to be done for `all'. >> make[6]: Leaving directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/components/call-history' >> Making all in gmconf-personal-details >> make[6]: Entering directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/components/gmconf-personal-details' >> make[6]: Nothing to be done for `all'. >> make[6]: Leaving directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/components/gmconf-personal-details' >> Making all in local-roster >> make[6]: Entering directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/components/local-roster' >> make[6]: Nothing to be done for `all'. >> make[6]: Leaving directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/components/local-roster' >> Making all in opal >> make[6]: Entering directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/components/opal' >> make[6]: Nothing to be done for `all'. >> make[6]: Leaving directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/components/opal' >> Making all in ptlib >> make[6]: Entering directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/components/ptlib' >> make[6]: Nothing to be done for `all'. >> make[6]: Leaving directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/components/ptlib' >> Making all in avahi-publisher >> make[6]: Entering directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/components/avahi-publisher' >> make[6]: Nothing to be done for `all'. >> make[6]: Leaving directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/components/avahi-publisher' >> Making all in avahi >> make[6]: Entering directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/components/avahi' >> make[6]: Nothing to be done for `all'. >> make[6]: Leaving directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/components/avahi' >> Making all in evolution >> make[6]: Entering directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/components/evolution' >> make[6]: Nothing to be done for `all'. >> make[6]: Leaving directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/components/evolution' >> Making all in ldap >> make[6]: Entering directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/components/ldap' >> make[6]: Nothing to be done for `all'. >> make[6]: Leaving directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/components/ldap' >> make[6]: Entering directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/components' >> make[6]: Nothing to be done for `all-am'. >> make[6]: Leaving directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/components' >> make[5]: Leaving directory >> `/home/khalfan/build-hardy/ekiga/lib/engine/components' >> make[5]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine' >> make[5]: Nothing to be done for `all-am'. >> make[5]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine' >> make[4]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine' >> make[4]: Entering directory `/home/khalfan/build-hardy/ekiga/lib' >> make[4]: Nothing to be done for `all-am'. >> make[4]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib' >> make[3]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib' >> make[2]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib' >> Making all in src >> make[2]: Entering directory `/home/khalfan/build-hardy/ekiga/src' >> make all-am >> make[3]: Entering directory `/home/khalfan/build-hardy/ekiga/src' >> g++ -DHAVE_CONFIG_H -I. -I.. -I../lib -I../lib/gmconf -I../lib/toolbox >> -I../lib/gui -I../lib/engine/ -I../lib/engine/framework >> -I../lib/engine/gui/gtk-frontend -I../lib/engine/account/skel >> -I../lib/engine/addressbook/skel -I../lib/engine/chat/skel >> -I../lib/engine/presence/skel -I../lib/engine/protocol/skel >> -I../lib/engine/protocol/sip -I../lib/engine/videooutput/skel >> -I../lib/engine/videoinput/skel -I../lib/engine/audioinput/skel >> -I../lib/engine/audiooutput/skel -I../lib/engine/hal/skel >> -I../lib/engine/framework -I../lib/engine/gui/gtk-core >> -I../lib/engine/components/opal -I../src -I../src/dbus-helper/ >> -I../src/gui/ -I.. -DSCHEMA_AGE=62 -I../lib/engine/videooutput/common >> -I../lib/engine/videooutput/x -I/usr/include/gtk-2.0 >> -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo >> -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 >> -I/usr/lib/glib-2.0/include -I/usr/include/freetype2 >> -I/usr/include/libpng12 -I/usr/include/pixman-1 >> -DGDK_PIXBUF_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED >> -DGTK_DISABLE_DEPRECATED -DGDK_PIXBUF_DISABLE_SINGLE_INCLUDES >> -DGTK_DISABLE_SINGLE_INCLUDES -pthread -I/usr/include/glib-2.0 >> -I/usr/lib/glib-2.0/include -DG_DISABLE_SINGLE_INCLUDES -DORBIT2=1 >> -pthread -I/usr/include/libgnome-2.0 -I/usr/include/orbit-2.0 >> -I/usr/include/gconf/2 -I/usr/include/gnome-vfs-2.0 >> -I/usr/lib/gnome-vfs-2.0/include -I/usr/include/glib-2.0 >> -I/usr/lib/glib-2.0/include -I/usr/include/libbonobo-2.0 >> -I/usr/include/bonobo-activation-2.0 -I/usr/include/libgnomeui-2.0 >> -I/usr/include/libart-2.0 -I/usr/include/gnome-keyring-1 >> -I/usr/include/libbonoboui-2.0 -I/usr/include/libgnomecanvas-2.0 >> -I/usr/include/gtk-2.0 -I/usr/include/libxml2 -I/usr/include/pango-1.0 >> -I/usr/include/gail-1.0 -I/usr/include/freetype2 >> -I/usr/include/atk-1.0 -I/usr/lib/gtk-2.0/include -I/usr/include/cairo >> -I/usr/include/libpng12 -I/usr/include/pixman-1 >> -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include >> -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DPTRACING=1 >> -D_REENTRANT -fno-exceptions -I/usr/include/opal -DPTRACING=1 >> -D_REENTRANT -fno-exceptions -I/usr/include/sigc++-2.0 >> -I/usr/lib/sigc++-2.0/include -I/usr/include/libxml2 -g -O2 -Wall >> -Wextra -Winit-self -Wswitch-default -Wswitch-enum -Wstrict-aliasing=2 >> -Wfloat-equal -Wshadow -MT main.o -MD -MP -MF .deps/main.Tpo -c -o >> main.o `test -f 'gui/main.cpp' || echo './'`gui/main.cpp >> gui/main.cpp: In function 'int main(int, char**, char**)': >> gui/main.cpp:4350: error: cannot call member function 'void >> PProcess::PreInitialise(int, char**, char**)' without object >> make[3]: *** [main.o] Error 1 >> make[3]: Leaving directory `/home/khalfan/build-hardy/ekiga/src' >> make[2]: *** [all] Error 2 >> make[2]: Leaving directory `/home/khalfan/build-hardy/ekiga/src' >> make[1]: *** [all-recursive] Error 1 >> make[1]: Leaving directory `/home/khalfan/build-hardy/ekiga' >> make: *** [all] Error 2 >> > > You are compiling ekiga 3.0.1 with OPAL and PTLIB TRUNK. Either use the stable releases for all of them, > or the TRUNK releases for all of them, but don't mix them together. > can you tell me where i can get the stable release for opal and ptlib or the TRUNK release for ekiga? thanks From Eugen.Dedu at pu-pm.univ-fcomte.fr Tue Dec 9 15:54:31 2008 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Tue, 09 Dec 2008 16:54:31 +0100 Subject: [Ekiga-list] can't compile ekiga 3.0.1 ubuntu hardy In-Reply-To: <493E8DBD.4060204@gmail.com> References: <1228718964.31538.0.camel@scorpion.multitel.be> <1228812084.31538.32.camel@scorpion.multitel.be> <493E8DBD.4060204@gmail.com> Message-ID: <493E94B7.70206@pu-pm.univ-fcomte.fr> For stable : http://wiki.ekiga.org/index.php/Linux_Users (look at the first 3 links). Eugen Ali wrote: > Damien Sandras wrote: >> Le lundi 08 d?cembre 2008 ? 20:39 +0300, Fedor vonBock a ?crit : >> >>> THanks for replying...this is the error that i get when i do "make", i >>> don't know why >>> >>> >>> ======================================================== >>> Now type `make' to compile ekiga >>> khalfan at khalfan-desktop:~/build-hardy/ekiga$ >>> khalfan at khalfan-desktop:~/build-hardy/ekiga$ sudo make >>> make all-recursive >>> make[1]: Entering directory `/home/khalfan/build-hardy/ekiga' >>> Making all in man >>> make[2]: Entering directory `/home/khalfan/build-hardy/ekiga/man' >>> make[2]: Nothing to be done for `all'. >>> make[2]: Leaving directory `/home/khalfan/build-hardy/ekiga/man' >>> Making all in sounds >>> make[2]: Entering directory `/home/khalfan/build-hardy/ekiga/sounds' >>> make[2]: Nothing to be done for `all'. >>> make[2]: Leaving directory `/home/khalfan/build-hardy/ekiga/sounds' >>> Making all in pixmaps >>> make[2]: Entering directory `/home/khalfan/build-hardy/ekiga/pixmaps' >>> make[2]: Nothing to be done for `all'. >>> make[2]: Leaving directory `/home/khalfan/build-hardy/ekiga/pixmaps' >>> Making all in lib >>> make[2]: Entering directory `/home/khalfan/build-hardy/ekiga/lib' >>> make all-recursive >>> make[3]: Entering directory `/home/khalfan/build-hardy/ekiga/lib' >>> Making all in gmconf >>> make[4]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/gmconf' >>> make[4]: Nothing to be done for `all'. >>> make[4]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/gmconf' >>> Making all in gui >>> make[4]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/gui' >>> make[5]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/gui' >>> make[5]: Nothing to be done for `all-am'. >>> make[5]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/gui' >>> make[4]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/gui' >>> Making all in toolbox >>> make[4]: Entering directory >>> `/home/khalfan/build-hardy/ekiga/lib/toolbox' >>> make[4]: Nothing to be done for `all'. >>> make[4]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/toolbox' >>> Making all in platform >>> make[4]: Entering directory >>> `/home/khalfan/build-hardy/ekiga/lib/platform' >>> make[4]: Nothing to be done for `all'. >>> make[4]: Leaving directory >>> `/home/khalfan/build-hardy/ekiga/lib/platform' >>> Making all in pixops >>> make[4]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/pixops' >>> make[4]: Nothing to be done for `all'. >>> make[4]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/pixops' >>> Making all in engine >>> make[4]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine' >>> Making all in framework >>> make[5]: Entering directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/framework' >>> make[5]: Nothing to be done for `all'. >>> make[5]: Leaving directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/framework' >>> Making all in account >>> make[5]: Entering directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/account' >>> Making all in skel >>> make[6]: Entering directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/account/skel' >>> make[6]: Nothing to be done for `all'. >>> make[6]: Leaving directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/account/skel' >>> make[6]: Entering directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/account' >>> make[6]: Nothing to be done for `all-am'. >>> make[6]: Leaving directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/account' >>> make[5]: Leaving directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/account' >>> Making all in addressbook >>> make[5]: Entering directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/addressbook' >>> Making all in skel >>> make[6]: Entering directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/addressbook/skel' >>> make[6]: Nothing to be done for `all'. >>> make[6]: Leaving directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/addressbook/skel' >>> make[6]: Entering directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/addressbook' >>> make[6]: Nothing to be done for `all-am'. >>> make[6]: Leaving directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/addressbook' >>> make[5]: Leaving directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/addressbook' >>> Making all in presence >>> make[5]: Entering directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/presence' >>> Making all in skel >>> make[6]: Entering directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/presence/skel' >>> make[6]: Nothing to be done for `all'. >>> make[6]: Leaving directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/presence/skel' >>> make[6]: Entering directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/presence' >>> make[6]: Nothing to be done for `all-am'. >>> make[6]: Leaving directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/presence' >>> make[5]: Leaving directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/presence' >>> Making all in chat >>> make[5]: Entering directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/chat' >>> Making all in skel >>> make[6]: Entering directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/chat/skel' >>> make[6]: Nothing to be done for `all'. >>> make[6]: Leaving directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/chat/skel' >>> Making all in echo >>> make[6]: Entering directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/chat/echo' >>> make[6]: Nothing to be done for `all'. >>> make[6]: Leaving directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/chat/echo' >>> make[6]: Entering directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/chat' >>> make[6]: Nothing to be done for `all-am'. >>> make[6]: Leaving directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/chat' >>> make[5]: Leaving directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/chat' >>> Making all in gui >>> make[5]: Entering directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/gui' >>> Making all in gtk-core >>> make[6]: Entering directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/gui/gtk-core' >>> make[6]: Nothing to be done for `all'. >>> make[6]: Leaving directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/gui/gtk-core' >>> Making all in gtk-frontend >>> make[6]: Entering directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/gui/gtk-frontend' >>> make[6]: Nothing to be done for `all'. >>> make[6]: Leaving directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/gui/gtk-frontend' >>> make[6]: Entering directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/gui' >>> make[6]: Nothing to be done for `all-am'. >>> make[6]: Leaving directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/gui' >>> make[5]: Leaving directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/gui' >>> Making all in protocol >>> make[5]: Entering directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/protocol' >>> Making all in skel >>> make[6]: Entering directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/protocol/skel' >>> make[6]: Nothing to be done for `all'. >>> make[6]: Leaving directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/protocol/skel' >>> make[6]: Entering directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/protocol' >>> make[6]: Nothing to be done for `all-am'. >>> make[6]: Leaving directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/protocol' >>> make[5]: Leaving directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/protocol' >>> Making all in videooutput >>> make[5]: Entering directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/videooutput' >>> Making all in skel >>> make[6]: Entering directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/videooutput/skel' >>> make[6]: Nothing to be done for `all'. >>> make[6]: Leaving directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/videooutput/skel' >>> Making all in x >>> make[6]: Entering directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/videooutput/x' >>> make[6]: Nothing to be done for `all'. >>> make[6]: Leaving directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/videooutput/x' >>> make[6]: Entering directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/videooutput' >>> make[6]: Nothing to be done for `all-am'. >>> make[6]: Leaving directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/videooutput' >>> make[5]: Leaving directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/videooutput' >>> Making all in videoinput >>> make[5]: Entering directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/videoinput' >>> Making all in skel >>> make[6]: Entering directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/videoinput/skel' >>> make[6]: Nothing to be done for `all'. >>> make[6]: Leaving directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/videoinput/skel' >>> Making all in mlogo >>> make[6]: Entering directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/videoinput/mlogo' >>> make[6]: Nothing to be done for `all'. >>> make[6]: Leaving directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/videoinput/mlogo' >>> make[6]: Entering directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/videoinput' >>> make[6]: Nothing to be done for `all-am'. >>> make[6]: Leaving directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/videoinput' >>> make[5]: Leaving directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/videoinput' >>> Making all in audioinput >>> make[5]: Entering directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/audioinput' >>> Making all in skel >>> make[6]: Entering directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/audioinput/skel' >>> make[6]: Nothing to be done for `all'. >>> make[6]: Leaving directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/audioinput/skel' >>> Making all in null >>> make[6]: Entering directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/audioinput/null' >>> make[6]: Nothing to be done for `all'. >>> make[6]: Leaving directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/audioinput/null' >>> make[6]: Entering directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/audioinput' >>> make[6]: Nothing to be done for `all-am'. >>> make[6]: Leaving directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/audioinput' >>> make[5]: Leaving directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/audioinput' >>> Making all in audiooutput >>> make[5]: Entering directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/audiooutput' >>> Making all in skel >>> make[6]: Entering directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/audiooutput/skel' >>> make[6]: Nothing to be done for `all'. >>> make[6]: Leaving directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/audiooutput/skel' >>> Making all in null >>> make[6]: Entering directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/audiooutput/null' >>> make[6]: Nothing to be done for `all'. >>> make[6]: Leaving directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/audiooutput/null' >>> make[6]: Entering directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/audiooutput' >>> make[6]: Nothing to be done for `all-am'. >>> make[6]: Leaving directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/audiooutput' >>> make[5]: Leaving directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/audiooutput' >>> Making all in hal >>> make[5]: Entering directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/hal' >>> Making all in skel >>> make[6]: Entering directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/hal/skel' >>> make[6]: Nothing to be done for `all'. >>> make[6]: Leaving directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/hal/skel' >>> Making all in dbus >>> make[6]: Entering directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/hal/dbus' >>> make all-am >>> make[7]: Entering directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/hal/dbus' >>> make[7]: Nothing to be done for `all-am'. >>> make[7]: Leaving directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/hal/dbus' >>> make[6]: Leaving directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/hal/dbus' >>> make[6]: Entering directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/hal' >>> make[6]: Nothing to be done for `all-am'. >>> make[6]: Leaving directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/hal' >>> make[5]: Leaving directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/hal' >>> Making all in components >>> make[5]: Entering directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/components' >>> Making all in call-history >>> make[6]: Entering directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/components/call-history' >>> make[6]: Nothing to be done for `all'. >>> make[6]: Leaving directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/components/call-history' >>> Making all in gmconf-personal-details >>> make[6]: Entering directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/components/gmconf-personal-details' >>> >>> make[6]: Nothing to be done for `all'. >>> make[6]: Leaving directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/components/gmconf-personal-details' >>> >>> Making all in local-roster >>> make[6]: Entering directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/components/local-roster' >>> make[6]: Nothing to be done for `all'. >>> make[6]: Leaving directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/components/local-roster' >>> Making all in opal >>> make[6]: Entering directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/components/opal' >>> make[6]: Nothing to be done for `all'. >>> make[6]: Leaving directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/components/opal' >>> Making all in ptlib >>> make[6]: Entering directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/components/ptlib' >>> make[6]: Nothing to be done for `all'. >>> make[6]: Leaving directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/components/ptlib' >>> Making all in avahi-publisher >>> make[6]: Entering directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/components/avahi-publisher' >>> make[6]: Nothing to be done for `all'. >>> make[6]: Leaving directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/components/avahi-publisher' >>> Making all in avahi >>> make[6]: Entering directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/components/avahi' >>> make[6]: Nothing to be done for `all'. >>> make[6]: Leaving directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/components/avahi' >>> Making all in evolution >>> make[6]: Entering directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/components/evolution' >>> make[6]: Nothing to be done for `all'. >>> make[6]: Leaving directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/components/evolution' >>> Making all in ldap >>> make[6]: Entering directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/components/ldap' >>> make[6]: Nothing to be done for `all'. >>> make[6]: Leaving directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/components/ldap' >>> make[6]: Entering directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/components' >>> make[6]: Nothing to be done for `all-am'. >>> make[6]: Leaving directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/components' >>> make[5]: Leaving directory >>> `/home/khalfan/build-hardy/ekiga/lib/engine/components' >>> make[5]: Entering directory `/home/khalfan/build-hardy/ekiga/lib/engine' >>> make[5]: Nothing to be done for `all-am'. >>> make[5]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine' >>> make[4]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib/engine' >>> make[4]: Entering directory `/home/khalfan/build-hardy/ekiga/lib' >>> make[4]: Nothing to be done for `all-am'. >>> make[4]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib' >>> make[3]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib' >>> make[2]: Leaving directory `/home/khalfan/build-hardy/ekiga/lib' >>> Making all in src >>> make[2]: Entering directory `/home/khalfan/build-hardy/ekiga/src' >>> make all-am >>> make[3]: Entering directory `/home/khalfan/build-hardy/ekiga/src' >>> g++ -DHAVE_CONFIG_H -I. -I.. -I../lib -I../lib/gmconf -I../lib/toolbox >>> -I../lib/gui -I../lib/engine/ -I../lib/engine/framework >>> -I../lib/engine/gui/gtk-frontend -I../lib/engine/account/skel >>> -I../lib/engine/addressbook/skel -I../lib/engine/chat/skel >>> -I../lib/engine/presence/skel -I../lib/engine/protocol/skel >>> -I../lib/engine/protocol/sip -I../lib/engine/videooutput/skel >>> -I../lib/engine/videoinput/skel -I../lib/engine/audioinput/skel >>> -I../lib/engine/audiooutput/skel -I../lib/engine/hal/skel >>> -I../lib/engine/framework -I../lib/engine/gui/gtk-core >>> -I../lib/engine/components/opal -I../src -I../src/dbus-helper/ >>> -I../src/gui/ -I.. -DSCHEMA_AGE=62 -I../lib/engine/videooutput/common >>> -I../lib/engine/videooutput/x -I/usr/include/gtk-2.0 >>> -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo >>> -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 >>> -I/usr/lib/glib-2.0/include -I/usr/include/freetype2 >>> -I/usr/include/libpng12 -I/usr/include/pixman-1 >>> -DGDK_PIXBUF_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED >>> -DGTK_DISABLE_DEPRECATED -DGDK_PIXBUF_DISABLE_SINGLE_INCLUDES >>> -DGTK_DISABLE_SINGLE_INCLUDES -pthread -I/usr/include/glib-2.0 >>> -I/usr/lib/glib-2.0/include -DG_DISABLE_SINGLE_INCLUDES -DORBIT2=1 >>> -pthread -I/usr/include/libgnome-2.0 -I/usr/include/orbit-2.0 >>> -I/usr/include/gconf/2 -I/usr/include/gnome-vfs-2.0 >>> -I/usr/lib/gnome-vfs-2.0/include -I/usr/include/glib-2.0 >>> -I/usr/lib/glib-2.0/include -I/usr/include/libbonobo-2.0 >>> -I/usr/include/bonobo-activation-2.0 -I/usr/include/libgnomeui-2.0 >>> -I/usr/include/libart-2.0 -I/usr/include/gnome-keyring-1 >>> -I/usr/include/libbonoboui-2.0 -I/usr/include/libgnomecanvas-2.0 >>> -I/usr/include/gtk-2.0 -I/usr/include/libxml2 -I/usr/include/pango-1.0 >>> -I/usr/include/gail-1.0 -I/usr/include/freetype2 >>> -I/usr/include/atk-1.0 -I/usr/lib/gtk-2.0/include -I/usr/include/cairo >>> -I/usr/include/libpng12 -I/usr/include/pixman-1 >>> -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include >>> -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DPTRACING=1 >>> -D_REENTRANT -fno-exceptions -I/usr/include/opal -DPTRACING=1 >>> -D_REENTRANT -fno-exceptions -I/usr/include/sigc++-2.0 >>> -I/usr/lib/sigc++-2.0/include -I/usr/include/libxml2 -g -O2 -Wall >>> -Wextra -Winit-self -Wswitch-default -Wswitch-enum -Wstrict-aliasing=2 >>> -Wfloat-equal -Wshadow -MT main.o -MD -MP -MF .deps/main.Tpo -c -o >>> main.o `test -f 'gui/main.cpp' || echo './'`gui/main.cpp >>> gui/main.cpp: In function 'int main(int, char**, char**)': >>> gui/main.cpp:4350: error: cannot call member function 'void >>> PProcess::PreInitialise(int, char**, char**)' without object >>> make[3]: *** [main.o] Error 1 >>> make[3]: Leaving directory `/home/khalfan/build-hardy/ekiga/src' >>> make[2]: *** [all] Error 2 >>> make[2]: Leaving directory `/home/khalfan/build-hardy/ekiga/src' >>> make[1]: *** [all-recursive] Error 1 >>> make[1]: Leaving directory `/home/khalfan/build-hardy/ekiga' >>> make: *** [all] Error 2 >>> >> >> You are compiling ekiga 3.0.1 with OPAL and PTLIB TRUNK. Either use >> the stable releases for all of them, >> or the TRUNK releases for all of them, but don't mix them together. >> > can you tell me where i can get the stable release for opal and ptlib or > the TRUNK release for ekiga? From dsandras at seconix.com Tue Dec 9 20:23:27 2008 From: dsandras at seconix.com (Damien Sandras) Date: Tue, 09 Dec 2008 21:23:27 +0100 Subject: [Ekiga-list] Ekiga version 2.0.12 no longer compatible with ekiga.net? In-Reply-To: <200812082217.32235.calie@uwaterloo.ca> References: <200812082217.32235.calie@uwaterloo.ca> Message-ID: <1228854207.31538.154.camel@scorpion.multitel.be> Le lundi 08 d?cembre 2008 ? 22:17 +1100, Colin Alie a ?crit : > Good evening Damien and Palo, > > Thanks for your replies. > > Damien, I'm sorry the expected debugging information was not included in my > last message. I've since installed the correct libraries. I've attached to > this message the file ekiga.log which contains the output from a session in > which the following actions were taken: > - started ekiga ($ ekiga -d 4 2> ekiga.log) > - Edit-->Accounts and activated ekiga.net account > - dialed 500 at ekiga.net > - waited for call to connect and said a few words > - terminated call > - quit Ekiga > > Palo, I read the thread "remote user cleared the call" that you started late > November. I've taken your comment regarding NAT to heart. Connecting my > laptop directly to the Internet was on my list of things to try as I'm able > to use Ekiga on my workstation at work which has a public IP address. > > One more thing...whenever I register to any account using Ekiga, I always see > two messages in the General History confirming registration. Does this imply > anything? > > Anyway, thanks for your help. There are a few things I do not understand : 1) the following 2008/12/08 21:52:44.348 2:37.091 SIP Transport:8527488 SIP Bad Request-Line received on udp$86.64.162.35:5060 2008/12/08 21:52:44.349 2:37.091 SIP Transport:8527488 SIP Malformed request received on udp$86.64.162.35:5060 It tells you are receiving a malformed request from ekiga.net, right after you have sent the initial request yourself. But Ekiga.net is not sending anything yet. 2) it thinks the Malformed Packet is related to the INVITE 3) NAT settings are ok, but you are receiving no audio 4) 2.0.12 works for a few hundreds other users Do you have a way to try 3.0 ? -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From Gene.Reed at Embarq.com Tue Dec 9 22:26:41 2008 From: Gene.Reed at Embarq.com (Reed, Gene R [EQ]) Date: Tue, 9 Dec 2008 16:26:41 -0600 Subject: [Ekiga-list] Ekiga fails SIP registration Message-ID: I've installed Ekiga on OpenSUSE 11, configured it with the same authentication used with other softphone installations on the same system, but Ekiga fails to register with my SIP service (not the Ekiga service). Additionally, the documentation and faq seem not to be available when I attempt to use it. Any advice would be appreciated. Thanks, Gene -------------- next part -------------- An HTML attachment was scrubbed... URL: From billcollins1.2007 at gmail.com Wed Dec 10 14:30:55 2008 From: billcollins1.2007 at gmail.com (Bill Collins) Date: Wed, 10 Dec 2008 09:30:55 -0500 Subject: [Ekiga-list] Installing update Message-ID: <33efb16e0812100630g307b0845wa576f394d342292f@mail.gmail.com> Please advise best procedure to follow to install the latest update. Currently using 2.0.12 that came with Ubuntu 8.04-1 I'm a beginner to all this. tia Bill Collins -------------- next part -------------- An HTML attachment was scrubbed... URL: From f.vonbock at gmail.com Wed Dec 10 14:59:00 2008 From: f.vonbock at gmail.com (Fedor vonBock) Date: Wed, 10 Dec 2008 17:59:00 +0300 Subject: [Ekiga-list] could not register : behind a router Message-ID: Hello, I have successfully compiled and run ekiga (albeit with admin privilege). However, I am not able to connect. The bar below has the message (could not register sip:@ekiga.net. I am behind a US robotics router and i want to know if that's significant. From oisin.feeley at gmail.com Wed Dec 10 17:17:10 2008 From: oisin.feeley at gmail.com (Oisin Feeley) Date: Wed, 10 Dec 2008 12:17:10 -0500 Subject: [Ekiga-list] could not register : behind a router In-Reply-To: References: Message-ID: On Wed, Dec 10, 2008 at 9:59 AM, Fedor vonBock wrote: > Hello, > > I have successfully compiled and run ekiga (albeit with admin > privilege). However, I am not able to connect. The bar below has the > message (could not register sip:@ekiga.net. > > I am behind a US robotics router and i want to know if that's significant. There are lots of issues with being behind routers doing NAT. It is not possible to tell from the information you gave which specific one applies to your case -- US Robotics makes many different models and any specific model could be configured in a myriad of ways. Ekiga handles many of the issues pretty well by using STUN. You need to run the Configuration Assistant[0] to see what information it can tell you about what type of NAT you may be experiencing. See the wiki [1] for more information on NAT specifically. Good luck and ask on the list again if you still have trouble after experimenting and reading a bit. 0. http://wiki.ekiga.org/index.php/Configuring_Ekiga 1. http://wiki.ekiga.org/index.php/Ekiga_behind_a_NAT_router Best wishes, Oisin Feeley From palos at post.sk Wed Dec 10 23:46:27 2008 From: palos at post.sk (Palo S.) Date: 11 Dec 2008 00:46:27 +0100 (CET) Subject: [Ekiga-list] \"remote user cleared the call\" problem Message-ID: <494054D3.000001.32643@kamasutra> So finally I ran Wireshark. It confirmed that there is no CANCEL from the caller, yet Kamailio sends CANCEL to the called side. It also shows that Kamailio sends and resends INVITE to several ports and keeps sending them until 200 OK. After that Kamailio sends CANCEL. Is it trying to cancel a parallel branch? The Wireshark files are accessible at ftp://quacka.no-ip.org/pub/ekiga-called-packets-sipfiltered ftp://quacka.no-ip.org/pub/ekiga-caller-packets-sipfiltered P.S. some packets are segmented, use SIP filtering in Wireshark to display them properly ----- Origin?lna Spr?va ----- Od: Damien Sandras Komu: Ekiga mailing list Poslan?: 02.12.2008 13:09 Predmet: Re: [Ekiga-list] \\\"remote user cleared the call\\\" problem > Le mardi 02 d??cembre 2008 ?? 11:19 +0100, Palo S. a ??crit : > > > > > > A cancel can be sent if you are using forking, ie 2 Ekiga registered > > > with the same account name, from 2 different IP addresses and ports. As > > > soon as one answers, a CANCEL is sent to the other one. > > > > > > Couldn\\\'t it be the case ? > > > > It could be that due to a problem with NAT a private > > IP communicates with the server as well as the public > > IP. I can probably only say after I sniff the > > communication. I will run a sniffer when I have time > > and let you know if I find something interesting. It > > is also interesting that with Ekiga 2.0.12 (on called > > side) it behaves differently - I have not had a look > > at d4 yet but it looked like caller (thought that) > > estabilished a SIP connection but called side not > > (it continued to ring on the called side, even after > > cancelling the call on the caller side). > > > > In any case, it worked fine with the previous server, > > so there must be a way to either fix or at least > > workaround the problem on the code level (either server > > or maybe also client) which would be nice at least because > > of ordinary users that do not know/wish to play around > > with port forwarding (all ports forwarding was > > originally enabled by the provider in this case, not by > > the user...) > > > > If only I understood what really happens... Unfortunately, it is not the > case :( > -- > _ Damien Sandras > (o- > //\\ Ekiga Softphone : http://www.ekiga.org/ > v_/_ Be IP : http://www.beip.be/ > FOSDEM : http://www.fosdem.org/ > SIP Phone : sip:dsandras at ekiga.net > > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list __________ Najoriginalnejsie technologicke hracky - http://pocitace.sme.sk/ From ML at Bartschnet.de Thu Dec 11 02:23:29 2008 From: ML at Bartschnet.de (Rene Bartsch) Date: Thu, 11 Dec 2008 03:23:29 +0100 (CET) Subject: [Ekiga-list] how to bypass SIP server and call a computer directly? In-Reply-To: <86ej0hlqh0.fsf@blueyonder.co.uk> References: <864p1emtoy.fsf@blueyonder.co.uk> <86vdtul5b6.fsf@blueyonder.co.uk> <9b7373816d605022ce585a5e783403dd.squirrel@www.bartschnet.de> <86ej0hlqh0.fsf@blueyonder.co.uk> Message-ID: > "Rene Bartsch" writes: > What does Ekiga do with a user name on an incoming call? Just ignore > it? As Ekiga doesn't have a user management, I assume so. > What happens in general when the user name is left out? Calling Ekiga by IP/domain worked fine for me (haven't tested 3.x series, yet). >> But there's one special case in Ekiga. Alphanumeric addresses are >> interpreted as "sip:" while numeric-only addresses are interpreted >> as ENUM addresses. > > Thanks for this info! > > Does this mean that "1234" is equivalent to "enum:1234"? Is there > some standard prefix like ???enum:??? that is used for ENUM addresses? http://wiki.ekiga.org/index.php/Enum ;) Renne From j_reab1 at yahoo.com Thu Dec 11 04:12:10 2008 From: j_reab1 at yahoo.com (James Garvin) Date: Wed, 10 Dec 2008 20:12:10 -0800 (PST) Subject: [Ekiga-list] could not register : behind a router In-Reply-To: Message-ID: <380681.85679.qm@web38303.mail.mud.yahoo.com> I have tested Ekiga behind a router and it failed.. ?After going to ?directly to the network it worked ?fine. ?Unfortinuatly, ?I ?have two options now. Buy a second PC ?for my firewall and sanity (Virus) and one for ?a great phone service for linux ?which will be open to all prediators. I have tried to open ports and tested shorewall to no ?avil --- On Wed, 12/10/08, Fedor vonBock wrote: From: Fedor vonBock Subject: [Ekiga-list] could not register : behind a router To: "Ekiga mailing list" Date: Wednesday, December 10, 2008, 8:59 AM Hello, I have successfully compiled and run ekiga (albeit with admin privilege). However, I am not able to connect. The bar below has the message (could not register sip:@ekiga.net. I am behind a US robotics router and i want to know if that's significant. _______________________________________________ ekiga-list mailing list ekiga-list at gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list -------------- next part -------------- An HTML attachment was scrubbed... URL: From michel.memeteau at gmail.com Thu Dec 11 09:28:25 2008 From: michel.memeteau at gmail.com (michel memeteau) Date: Thu, 11 Dec 2008 10:28:25 +0100 Subject: [Ekiga-list] could not register : behind a router In-Reply-To: <380681.85679.qm@web38303.mail.mud.yahoo.com> References: <380681.85679.qm@web38303.mail.mud.yahoo.com> Message-ID: On Thu, Dec 11, 2008 at 5:12 AM, James Garvin wrote: > I have tested Ekiga behind a router and it failed.. After going to > directly to the network it worked fine. Unfortinuatly, I have two > options now. Buy a second PC for my firewall and sanity (Virus) and one for > a great phone service for linux which will be open to all prediators. I > have tried to open ports and tested shorewall to no avil > James , your problem IS an issue and should be resolved. At least you should be able to register , even if after you have som problems with the audio streams. Can't you check the router configuraion ? From dsandras at seconix.com Thu Dec 11 17:58:21 2008 From: dsandras at seconix.com (Damien Sandras) Date: Thu, 11 Dec 2008 18:58:21 +0100 Subject: [Ekiga-list] \"remote user cleared the call\" problem In-Reply-To: <494054D3.000001.32643@kamasutra> References: <494054D3.000001.32643@kamasutra> Message-ID: <1229018301.25388.17.camel@scorpion.multitel.be> Le jeudi 11 d?cembre 2008 ? 00:46 +0100, Palo S. a ?crit : > So finally I ran Wireshark. It confirmed that there > is no CANCEL from the caller, yet Kamailio sends > CANCEL to the called side. It also shows that > Kamailio sends and resends INVITE to several ports > and keeps sending them until 200 OK. After that > Kamailio sends CANCEL. Is it trying to cancel > a parallel branch? > The Wireshark files are accessible at > ftp://quacka.no-ip.org/pub/ekiga-called-packets-sipfiltered > ftp://quacka.no-ip.org/pub/ekiga-caller-packets-sipfiltered > > P.S. some packets are segmented, use SIP filtering > in Wireshark to display them properly > I wonder if we should just not ignore the cancel... -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From palos at post.sk Thu Dec 11 21:15:51 2008 From: palos at post.sk (Palo S.) Date: 11 Dec 2008 22:15:51 +0100 (CET) Subject: [Ekiga-list] \"remote user cleared the call\" problem Message-ID: <49418307.000001.12038@kamasutra> > > I wonder if we should just not ignore the cancel... > -- It seems that proper fix should be done on Kamailio. Ignoring CANCEL for INVITE could be a workaround in the meantime, however it would probably cause problems in situations when invite should be cancelled (ie when the other side cancels indeed or in case of multiple branches)? Palo __________ http://www.tahaj.sk - Stiahnite si najnovsie verzie vasich oblubenych programov From dsandras at seconix.com Thu Dec 11 21:27:51 2008 From: dsandras at seconix.com (Damien Sandras) Date: Thu, 11 Dec 2008 22:27:51 +0100 Subject: [Ekiga-list] \"remote user cleared the call\" problem In-Reply-To: <49418307.000001.12038@kamasutra> References: <49418307.000001.12038@kamasutra> Message-ID: <1229030871.25388.49.camel@scorpion.multitel.be> Le jeudi 11 d?cembre 2008 ? 22:15 +0100, Palo S. a ?crit : > > > > I wonder if we should just not ignore the cancel... > > -- > > It seems that proper fix should be done on Kamailio. > Ignoring CANCEL for INVITE could be a workaround in > the meantime, however it would probably cause > problems in situations when invite should be cancelled > (ie when the other side cancels indeed or in case > of multiple branches)? > Not sure how to fix Kamailio, but I wonder if the CANCEL is not taken into account when it should not 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:dsandras at ekiga.net From palos at post.sk Thu Dec 11 21:55:14 2008 From: palos at post.sk (Palo S.) Date: 11 Dec 2008 22:55:14 +0100 (CET) Subject: [Ekiga-list] \"remote user cleared the call\" problem Message-ID: <49418C42.000001.15677@kamasutra> > > Not sure how to fix Kamailio It may be possible for Kamailio developers to identify place (in the code) where Kamailio sends this CANCEL by itself and fix... > but I wonder if the CANCEL is not taken > into account when it should not be. I think that Ekiga does it correctly, at least I can\'t see why should it not take it into account. If there is a safe way to distinguish between \"correct\" and \"incorrect\" CANCEL then of course, however I don\'t know how that could be done 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:dsandras at ekiga.net > > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list __________ http://sport.sme.sk - Najkomplexnej?ie inform?cie zo ?portu From phil-ekiga at tinsleyviaduct.com Thu Dec 11 23:10:12 2008 From: phil-ekiga at tinsleyviaduct.com (Phil Reynolds) Date: Thu, 11 Dec 2008 23:10:12 +0000 Subject: [Ekiga-list] h263 in Debian lenny / bare number dial Message-ID: <20081211231012.18782i2xw8099uxg@topdeck.tinsleyviaduct.com> I am trying to get ekiga to work in Debian lenny, with the H263 codec, but when I build opal, H263 is not supported. I am currently backporting packages from experimental. What do I need to do to get h263? Is there a better way to do this, remaining otherwise on lenny? With ekiga 2.*, I could send sip:number to my Asterisk box and it would dial that number in the context. I have to put @fqdn on the end now for that to work - is there, or will there be, a way to fix this? -- Phil Reynolds mail: phil-ekiga at tinsleyviaduct.com Web: http://www.tinsleyviaduct.com/phil/ Waltham 66, Emley Moor 69, Droitwich 79, Windows 95 ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. From f.vonbock at gmail.com Fri Dec 12 18:17:26 2008 From: f.vonbock at gmail.com (Fedor vonBock) Date: Fri, 12 Dec 2008 21:17:26 +0300 Subject: [Ekiga-list] could not register : behind a router In-Reply-To: References: <380681.85679.qm@web38303.mail.mud.yahoo.com> Message-ID: is ekiga expecting something on any incoming port when registering that i need to enable on my router? That's the main problem now main message is "could not register alikhalfan1 at ekiga.net" (i check the account status and it says timeout. On 12/11/08, michel memeteau wrote: > On Thu, Dec 11, 2008 at 5:12 AM, James Garvin wrote: >> I have tested Ekiga behind a router and it failed.. After going to >> directly to the network it worked fine. Unfortinuatly, I have two >> options now. Buy a second PC for my firewall and sanity (Virus) and one >> for >> a great phone service for linux which will be open to all prediators. I >> have tried to open ports and tested shorewall to no avil >> > > James , your problem IS an issue and should be resolved. > > At least you should be able to register , even if after you have som > problems with the audio streams. > > Can't you check the router configuraion ? > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > From calie at uwaterloo.ca Fri Dec 12 21:04:24 2008 From: calie at uwaterloo.ca (Colin Alie) Date: Sat, 13 Dec 2008 08:04:24 +1100 Subject: [Ekiga-list] Ekiga version 2.0.12 no longer compatible with ekiga.net? Message-ID: <200812130804.24760.calie@uwaterloo.ca> Good evening, Palo, as per your suggestion, I upgraded to Ekiga 3.0. However, I'm still unable to complete the echo test. Here's what I did in detail: - I'm currently running Ubuntu Hardy Heron - Yannick Defais has a PPA for Ekiga (https://launchpad.net/~sevmek/+archive). I added his repository to my sources.list - I prepared my system for compiling an updated Ekiga package: $ sudo apt-get update $ sudo apt-get build-dep ekiga $ sudo apt-get source ekiga - I built the version 3.0.0 of ekiga $ cd ekiga-3.0 $ ./configure; debian/rules build; fakeroot debian/rules binary $ cd .. - I installed the new version $ dpkg --install ekiga_3.0.0-0~0hardy37_i386.deb \ ekiga-dbg_3.0.0-0~0hardy37_i386.deb ekiga-doc_3.0.0-0~0hardy37_all.deb I've attached to this message the file ekiga-3.0.log which contains the output from a session in which the following actions were taken: - started ekiga ($ ekiga -d 4 2> ekiga-3.0.log) - Edit-->Accounts and activated ekiga.net account - dialed 500 at ekiga.net - the call seemed to connect and then disconnected immediately - quit Ekiga Anyway, thanks for your help. Until next time, Colin. -------------- next part -------------- A non-text attachment was scrubbed... Name: ekiga-3.0.log.gz Type: application/x-gzip Size: 22150 bytes Desc: not available URL: From Eugen.Dedu at pu-pm.univ-fcomte.fr Sat Dec 13 11:43:19 2008 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Sat, 13 Dec 2008 12:43:19 +0100 Subject: [Ekiga-list] Ekiga version 2.0.12 no longer compatible with ekiga.net? In-Reply-To: <200812130804.24760.calie@uwaterloo.ca> References: <200812130804.24760.calie@uwaterloo.ca> Message-ID: <49439FD7.6020808@pu-pm.univ-fcomte.fr> Colin Alie wrote: > Good evening, > > Palo, as per your suggestion, I upgraded to Ekiga 3.0. However, I'm still > unable to complete the echo test. Here's what I did in detail: > > - I'm currently running Ubuntu Hardy Heron > > - Yannick Defais has a PPA for Ekiga (https://launchpad.net/~sevmek/+archive). > I added his repository to my sources.list Hi, This repository contains ekiga from two months ago. It should be better to use a newer repository. Does someone know one? -- Eugen From Eugen.Dedu at pu-pm.univ-fcomte.fr Sat Dec 13 12:00:19 2008 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Sat, 13 Dec 2008 13:00:19 +0100 Subject: [Ekiga-list] h263 in Debian lenny / bare number dial In-Reply-To: <20081211231012.18782i2xw8099uxg@topdeck.tinsleyviaduct.com> References: <20081211231012.18782i2xw8099uxg@topdeck.tinsleyviaduct.com> Message-ID: <4943A3D3.7020704@pu-pm.univ-fcomte.fr> Hi, Phil Reynolds wrote: > I am trying to get ekiga to work in Debian lenny, with the H263 codec, > but when I build opal, H263 is not supported. I am currently backporting > packages from experimental. > > What do I need to do to get h263? Is there a better way to do this, > remaining otherwise on lenny? You must install libavcodec-dev not from debian (h263 is not dfsg), but from other site, for ex. http://debian-multimedia.org. > With ekiga 2.*, I could send sip:number to my Asterisk box and it would > dial that number in the context. I have to put @fqdn on the end now for > that to work - is there, or will there be, a way to fix this? I think that this automatic completion was removed, in order to have a proper address (think to e-mails: you put always the host address too). However, it has now an autocompletion feature (? la firefox). Cheers, -- Eugen From phil-ekiga at tinsleyviaduct.com Sat Dec 13 14:42:45 2008 From: phil-ekiga at tinsleyviaduct.com (Phil Reynolds) Date: Sat, 13 Dec 2008 14:42:45 +0000 Subject: [Ekiga-list] h263 in Debian lenny / bare number dial In-Reply-To: <4943A3D3.7020704@pu-pm.univ-fcomte.fr> References: <20081211231012.18782i2xw8099uxg@topdeck.tinsleyviaduct.com> <4943A3D3.7020704@pu-pm.univ-fcomte.fr> Message-ID: <20081213144245.15721gn47n4rbo4l@topdeck.tinsleyviaduct.com> Quoting "Eugen Dedu" : > Hi, > > Phil Reynolds wrote: >> I am trying to get ekiga to work in Debian lenny, with the H263 >> codec, but when I build opal, H263 is not supported. I am currently >> backporting packages from experimental. >> >> What do I need to do to get h263? Is there a better way to do this, >> remaining otherwise on lenny? > > You must install libavcodec-dev not from debian (h263 is not dfsg), > but from other site, for ex. http://debian-multimedia.org. It seems that ptlib wants libdc1394-13-dev and libavcodec-dev installs -22-dev - these are conflicting requirements that in turn cause there to be no h263. >> With ekiga 2.*, I could send sip:number to my Asterisk box and it >> would dial that number in the context. I have to put @fqdn on the >> end now for that to work - is there, or will there be, a way to fix >> this? > > I think that this automatic completion was removed, in order to have > a proper address (think to e-mails: you put always the host address > too). However, it has now an autocompletion feature (? la firefox). But you don't when mailing within the same system. Also, allowing a bare number would make it more telephone-like. Not doing so will make it difficult for another potential user here (not me). -- Phil Reynolds mail: phil-ekiga at tinsleyviaduct.com Web: http://www.tinsleyviaduct.com/phil/ Waltham 66, Emley Moor 69, Droitwich 79, Windows 95 ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. From Eugen.Dedu at pu-pm.univ-fcomte.fr Sat Dec 13 14:52:17 2008 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Sat, 13 Dec 2008 15:52:17 +0100 Subject: [Ekiga-list] h263 in Debian lenny / bare number dial In-Reply-To: <20081213144245.15721gn47n4rbo4l@topdeck.tinsleyviaduct.com> References: <20081211231012.18782i2xw8099uxg@topdeck.tinsleyviaduct.com> <4943A3D3.7020704@pu-pm.univ-fcomte.fr> <20081213144245.15721gn47n4rbo4l@topdeck.tinsleyviaduct.com> Message-ID: <4943CC21.8070804@pu-pm.univ-fcomte.fr> Phil Reynolds wrote: > Quoting "Eugen Dedu" : > >> Hi, >> >> Phil Reynolds wrote: >>> I am trying to get ekiga to work in Debian lenny, with the H263 >>> codec, but when I build opal, H263 is not supported. I am currently >>> backporting packages from experimental. >>> >>> What do I need to do to get h263? Is there a better way to do this, >>> remaining otherwise on lenny? >> >> You must install libavcodec-dev not from debian (h263 is not dfsg), >> but from other site, for ex. http://debian-multimedia.org. > > It seems that ptlib wants libdc1394-13-dev and libavcodec-dev installs > -22-dev - these are conflicting requirements that in turn cause there to > be no h263. Indeed (http://bugzilla.gnome.org/show_bug.cgi?id=545017). I always compile ptlib with libdc1394-13-dev, and install -22-dev right before compiling opal. >>> With ekiga 2.*, I could send sip:number to my Asterisk box and it >>> would dial that number in the context. I have to put @fqdn on the end >>> now for that to work - is there, or will there be, a way to fix this? >> >> I think that this automatic completion was removed, in order to have a >> proper address (think to e-mails: you put always the host address >> too). However, it has now an autocompletion feature (? la firefox). > > But you don't when mailing within the same system. Also, allowing a bare > number would make it more telephone-like. Not doing so will make it > difficult for another potential user here (not me). > I don't know... -- Eugen From palos at post.sk Sat Dec 13 15:25:29 2008 From: palos at post.sk (Palo S.) Date: 13 Dec 2008 16:25:29 +0100 (CET) Subject: [Ekiga-list] Ekiga version 2.0.12 no longer compatible with ekiga.net? Message-ID: <4943D3E9.000001.07352@kamasutra> > Palo, as per your suggestion, I upgraded to Ekiga 3.0. However, I\'m still I don\'t think it was my suggestion, anyway good that you tried it. Now after looking at your log I can bet that your issue is the same as I had in \'remote user cleared the call\' since Kamailio does exactly the same thing - from some reason it sends CANCEL on your behalf right after the call has been estabilished. (Also, I remember when I tried Ekiga 2, it resembled your problem with Ekiga 2). So we can be fairly certain to say it is a NAT related bug in Kamailio. You can still try to workaround it in a similar fashion as I did. Can you have a look at the port forwarding on your router, especially port 5060? In my case disabling port forwarding of 5060 did the trick... Palo __________ Najpopul?rnej?? blog na Slovensku - http://blog.sme.sk/ From f.vonbock at gmail.com Sat Dec 13 15:53:58 2008 From: f.vonbock at gmail.com (Fedor vonBock) Date: Sat, 13 Dec 2008 18:53:58 +0300 Subject: [Ekiga-list] could not register : behind a router In-Reply-To: References: <380681.85679.qm@web38303.mail.mud.yahoo.com> Message-ID: ok, I run ekiga with parameter -d 4 to capture the message and this is what i got (last lines) just to note that i registered successfully my diamondcard account using twinkle and was able to call the echo test (500 at ekiga.net) to interface 0 - "192.168.1.67%eth0" 2008/12/13 18:50:40.580 0:12.010 subscriber:0xb357ab90 SIP Transaction created. 2008/12/13 18:50:40.583 0:12.013 subscriber:0xb357ab90 DNS SRV Lookup sip.diamondcard.us service _sip._udp 2008/12/13 18:50:41.602 0:13.032 Housekeeper:0xb5878b90 SIP Set state Terminated_Timeout for transaction 1 REGISTER 2008/12/13 18:50:41.602 0:13.032 Housekeeper:0xb5878b90 SIP Changing REGISTER handler from Subscribing to Unavailable, target= sip:alikhalfan1 at ekiga.net , id=0e35fd72-9bc7-dd11-8a6f-001cc0223352 at khalfan-desktop 2008/12/13 18:50:41.602 0:13.032 Housekeeper:0xb5878b90 SIP Retrying REGISTER in 30 seconds. 2008/12/13 18:50:45.870 0:17.300 subscriber:0xb357ab90 SIP Transaction remote address is udp$62.4.81.186:5060 2008/12/13 18:50:45.871 0:17.301 subscriber:0xb357ab90 SIP Sending PDU (549 bytes) to: rem=udp$62.4.81.186:5060,local=udp$ 84.255.181.235:5060,if=192.168.1.67%eth0 REGISTER sip:sip.diamondcard.us SIP/2.0 CSeq: 2 REGISTER Via: SIP/2.0/UDP 84.255.181.235:5060 ;branch=z9hG4bK724e1376-9bc7-dd11-8a6f-001cc0223352;rport User-Agent: Ekiga/3.0.0 From: >;tag=5a481376-9bc7-dd11-8a6f-001cc0223352 Call-ID: c479fd72-9bc7-dd11-8a6f-001cc0223352 at khalfan-desktop To: > Contact: Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 3600 Content-Length: 0 Max-Forwards: 70 2008/12/13 18:50:45.871 0:17.301 subscriber:0xb357ab90 SIP Transaction timers set: retry=0.500, completion=6.000 2008/12/13 18:50:45.871 0:17.301 ThreadID:0xb357ab90 PWLib Destroyed thread 0x83751e0 subscriber:0xb357ab90(id = 0) 2008/12/13 18:50:46.371 0:17.801 Housekeeper:0xb5878b90 SIP Transaction 2 REGISTER timeout, making retry 1 2008/12/13 18:50:46.371 0:17.801 Housekeeper:0xb5878b90 OpalUDP Setting interface to 192.168.1.67%eth0 2008/12/13 18:50:46.372 0:17.802 Housekeeper:0xb5878b90 SIP Sending PDU (549 bytes) to: rem=udp$62.4.81.186:5060,local=udp$ 84.255.181.235:5060,if=192.168.1.67%eth0 REGISTER sip:sip.diamondcard.us SIP/2.0 CSeq: 2 REGISTER Via: SIP/2.0/UDP 84.255.181.235:5060 ;branch=z9hG4bK724e1376-9bc7-dd11-8a6f-001cc0223352;rport User-Agent: Ekiga/3.0.0 From: >;tag=5a481376-9bc7-dd11-8a6f-001cc0223352 Call-ID: c479fd72-9bc7-dd11-8a6f-001cc0223352 at khalfan-desktop To: > Contact: Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 3600 Content-Length: 0 Max-Forwards: 70 2008/12/13 18:50:46.372 0:17.802 Housekeeper:0xb5878b90 OpalUDP Setting interface to 192.168.1.67%eth0 2008/12/13 18:50:46.871 0:18.301 Opal Garbage:0xb58fab90 SIP Transaction 1 REGISTER destroyed. 2008/12/13 18:50:47.372 0:18.802 Housekeeper:0xb5878b90 SIP Transaction 2 REGISTER timeout, making retry 2 2008/12/13 18:50:47.372 0:18.802 Housekeeper:0xb5878b90 OpalUDP Setting interface to 192.168.1.67%eth0 2008/12/13 18:50:47.372 0:18.802 Housekeeper:0xb5878b90 SIP Sending PDU (549 bytes) to: rem=udp$62.4.81.186:5060,local=udp$ 84.255.181.235:5060,if=192.168.1.67%eth0 REGISTER sip:sip.diamondcard.us SIP/2.0 CSeq: 2 REGISTER Via: SIP/2.0/UDP 84.255.181.235:5060 ;branch=z9hG4bK724e1376-9bc7-dd11-8a6f-001cc0223352;rport User-Agent: Ekiga/3.0.0 From: >;tag=5a481376-9bc7-dd11-8a6f-001cc0223352 Call-ID: c479fd72-9bc7-dd11-8a6f-001cc0223352 at khalfan-desktop To: > Contact: Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 3600 Content-Length: 0 Max-Forwards: 70 2008/12/13 18:50:47.372 0:18.802 Housekeeper:0xb5878b90 OpalUDP Setting interface to 192.168.1.67%eth0 2008/12/13 18:50:49.372 0:20.802 Housekeeper:0xb5878b90 SIP Transaction 2 REGISTER timeout, making retry 3 2008/12/13 18:50:49.372 0:20.802 Housekeeper:0xb5878b90 OpalUDP Setting interface to 192.168.1.67%eth0 2008/12/13 18:50:49.372 0:20.802 Housekeeper:0xb5878b90 SIP Sending PDU (549 bytes) to: rem=udp$62.4.81.186:5060,local=udp$ 84.255.181.235:5060,if=192.168.1.67%eth0 REGISTER sip:sip.diamondcard.us SIP/2.0 CSeq: 2 REGISTER Via: SIP/2.0/UDP 84.255.181.235:5060 ;branch=z9hG4bK724e1376-9bc7-dd11-8a6f-001cc0223352;rport User-Agent: Ekiga/3.0.0 From: >;tag=5a481376-9bc7-dd11-8a6f-001cc0223352 Call-ID: c479fd72-9bc7-dd11-8a6f-001cc0223352 at khalfan-desktop To: > Contact: Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 3600 Content-Length: 0 Max-Forwards: 70 2008/12/13 18:50:49.372 0:20.802 Housekeeper:0xb5878b90 OpalUDP Setting interface to 192.168.1.67%eth0 2008/12/13 18:50:51.872 0:23.302 Housekeeper:0xb5878b90 SIP Set state Terminated_Timeout for transaction 2 REGISTER 2008/12/13 18:50:51.872 0:23.302 Housekeeper:0xb5878b90 SIP Changing REGISTER handler from Subscribing to Unavailable, target= sip:324278 at sip.diamondcard.us , id=c479fd72-9bc7-dd11-8a6f-001cc0223352 at khalfan-desktop 2008/12/13 18:50:51.872 0:23.302 Housekeeper:0xb5878b90 SIP Retrying REGISTER in 30 seconds. 2008/12/13 18:50:51.872 0:23.302 Opal Garbage:0xb58fab90 SIP Transaction 2 REGISTER destroyed. On Fri, Dec 12, 2008 at 9:17 PM, Fedor vonBock wrote: > is ekiga expecting something on any incoming port when registering > that i need to enable on my router? That's the main problem now > > main message is > > "could not register alikhalfan1 at ekiga.net" (i check the account > status and it says timeout. > > > > > > On 12/11/08, michel memeteau wrote: > > On Thu, Dec 11, 2008 at 5:12 AM, James Garvin wrote: > >> I have tested Ekiga behind a router and it failed.. After going to > >> directly to the network it worked fine. Unfortinuatly, I have two > >> options now. Buy a second PC for my firewall and sanity (Virus) and one > >> for > >> a great phone service for linux which will be open to all prediators. > I > >> have tried to open ports and tested shorewall to no avil > >> > > > > James , your problem IS an issue and should be resolved. > > > > At least you should be able to register , even if after you have som > > problems with the audio streams. > > > > Can't you check the router configuraion ? > > _______________________________________________ > > ekiga-list mailing list > > ekiga-list at gnome.org > > http://mail.gnome.org/mailman/listinfo/ekiga-list > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From hlelong at laposte.net Sat Dec 13 15:58:07 2008 From: hlelong at laposte.net (henri) Date: Sat, 13 Dec 2008 16:58:07 +0100 Subject: [Ekiga-list] ekiga-list Digest, Vol 29, Issue 18 In-Reply-To: References: Message-ID: <4943DB8F.1050207@laposte.net> Gros progr?s!!!!!!!! From phil-ekiga at tinsleyviaduct.com Sat Dec 13 18:43:52 2008 From: phil-ekiga at tinsleyviaduct.com (Phil Reynolds) Date: Sat, 13 Dec 2008 18:43:52 +0000 Subject: [Ekiga-list] h263 in Debian lenny / bare number dial In-Reply-To: <4943CC21.8070804@pu-pm.univ-fcomte.fr> References: <20081211231012.18782i2xw8099uxg@topdeck.tinsleyviaduct.com> <4943A3D3.7020704@pu-pm.univ-fcomte.fr> <20081213144245.15721gn47n4rbo4l@topdeck.tinsleyviaduct.com> <4943CC21.8070804@pu-pm.univ-fcomte.fr> Message-ID: <20081213184352.8335370fiojfxeg8@topdeck.tinsleyviaduct.com> Quoting "Eugen Dedu" : > Phil Reynolds wrote: >> Quoting "Eugen Dedu" : >> >>> Hi, >>> >>> Phil Reynolds wrote: >>>> I am trying to get ekiga to work in Debian lenny, with the H263 >>>> codec, but when I build opal, H263 is not supported. I am >>>> currently backporting packages from experimental. >>>> >>>> What do I need to do to get h263? Is there a better way to do >>>> this, remaining otherwise on lenny? >>> >>> You must install libavcodec-dev not from debian (h263 is not >>> dfsg), but from other site, for ex. http://debian-multimedia.org. >> >> It seems that ptlib wants libdc1394-13-dev and libavcodec-dev >> installs -22-dev - these are conflicting requirements that in turn >> cause there to be no h263. > > Indeed (http://bugzilla.gnome.org/show_bug.cgi?id=545017). I always > compile ptlib with libdc1394-13-dev, and install -22-dev right > before compiling opal. Still no h263 here even when I do that. -- Phil Reynolds mail: phil-ekiga at tinsleyviaduct.com Web: http://www.tinsleyviaduct.com/phil/ Waltham 66, Emley Moor 69, Droitwich 79, Windows 95 ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. From calie at uwaterloo.ca Sat Dec 13 22:59:53 2008 From: calie at uwaterloo.ca (Colin Alie) Date: Sun, 14 Dec 2008 09:59:53 +1100 Subject: [Ekiga-list] Ekiga version 2.0.12 no longer compatible with ekiga.net? Message-ID: <200812140959.54057.calie@uwaterloo.ca> Good evening, You're correct Palo. It was Damien who suggested upgrading to version 3.0. Sorry for the confusion and thanks for the continuing to follow this thread. > Can you have a look at the port forwarding on your router, especially port 5060? In my case disabling port forwarding of 5060 did the trick... By "disabling port forwarding of 5060", are you suggesting that I disable forwarding of incoming packets to port 5060 on the external interface of my modem/router to port 5060 of the laptop upon which Ekiga is running? At the moment, there are no port forwarding rules in place. Until next time, Colin. From peasthope at shaw.ca Sun Dec 14 17:40:06 2008 From: peasthope at shaw.ca (peasthope at shaw.ca) Date: Sun, 14 Dec 2008 09:40:06 -0800 Subject: [Ekiga-list] failure in registration of sip account Message-ID: Folk, This is Ekiga 2.0.12 in Debian Linuz. More often than not, my ekiga.net sip account fails to register automatically when the client initializes. There is never a problem registering manually in the Edit:Accounts window. Can anyone offer a solution? Thanks, ... Peter E. -- http://members.shaw.ca/peasthope/ http://carnot.yi.org/ = http://carnot.pathology.ubc.ca/ From bbagger at gmail.com Sun Dec 14 19:21:36 2008 From: bbagger at gmail.com (Bent) Date: Sun, 14 Dec 2008 20:21:36 +0100 Subject: [Ekiga-list] Ekiga cannot register with ekiga.net - Asterisk can Message-ID: <2e19719f0812141121o6f1a6617jec63b70a333f854a@mail.gmail.com> 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: bent at yosie ~ $ tshark -r ekiga-asterisk.trace Running as user "bent" and group "users". 1 0.000000 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 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) bent at yosie ~ $ whereas Ekiga the softphone doesn't: bent at yosie ~ $ tshark -r ekiga.trace Running as user "bent" and group "users". 1 0.000000 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:bentb at 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 bent at yosie ~ $ The full traces are available here (for about a month from now): http://filebin.ca/gnqnz/bentb-traces.tgz 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? 3. Why is the subscribe accepted '202 OK'? Kind regards, Bent From Eugen.Dedu at pu-pm.univ-fcomte.fr Sun Dec 14 19:24:39 2008 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Sun, 14 Dec 2008 20:24:39 +0100 Subject: [Ekiga-list] h263 in Debian lenny / bare number dial In-Reply-To: <20081213184352.8335370fiojfxeg8@topdeck.tinsleyviaduct.com> References: <20081211231012.18782i2xw8099uxg@topdeck.tinsleyviaduct.com> <4943A3D3.7020704@pu-pm.univ-fcomte.fr> <20081213144245.15721gn47n4rbo4l@topdeck.tinsleyviaduct.com> <4943CC21.8070804@pu-pm.univ-fcomte.fr> <20081213184352.8335370fiojfxeg8@topdeck.tinsleyviaduct.com> Message-ID: <49455D77.6080600@pu-pm.univ-fcomte.fr> Phil Reynolds wrote: > Quoting "Eugen Dedu" : > >> Phil Reynolds wrote: >>> Quoting "Eugen Dedu" : >>> >>>> Hi, >>>> >>>> Phil Reynolds wrote: >>>>> I am trying to get ekiga to work in Debian lenny, with the H263 >>>>> codec, but when I build opal, H263 is not supported. I am currently >>>>> backporting packages from experimental. >>>>> >>>>> What do I need to do to get h263? Is there a better way to do this, >>>>> remaining otherwise on lenny? >>>> >>>> You must install libavcodec-dev not from debian (h263 is not dfsg), >>>> but from other site, for ex. http://debian-multimedia.org. >>> >>> It seems that ptlib wants libdc1394-13-dev and libavcodec-dev >>> installs -22-dev - these are conflicting requirements that in turn >>> cause there to be no h263. >> >> Indeed (http://bugzilla.gnome.org/show_bug.cgi?id=545017). I always >> compile ptlib with libdc1394-13-dev, and install -22-dev right before >> compiling opal. > > Still no h263 here even when I do that. Please send the output of configure of opal. -- Eugen From palos at post.sk Mon Dec 15 00:24:30 2008 From: palos at post.sk (Palo S.) Date: 15 Dec 2008 01:24:30 +0100 (CET) Subject: [Ekiga-list] Ekiga version 2.0.12 no longer compatible with ekiga.net? Message-ID: <4945A3BE.000001.07103@kamasutra> ----- Origin?lna Spr?va ----- Od: Colin Alie Komu: Poslan?: 13.12.2008 23:59 Predmet: Re: [Ekiga-list] Ekiga version 2.0.12 no longer compatible withekiga.net? > Good evening, > > You\'re correct Palo. It was Damien who suggested upgrading to version 3.0. > Sorry for the confusion and thanks for the continuing to follow this thread. > > > Can you have a look at the port forwarding on your router, especially port > 5060? In my case disabling port forwarding of 5060 did the trick... > > By \"disabling port forwarding of 5060\", are you suggesting that I disable > forwarding of incoming packets to port 5060 on the external interface of my > modem/router to port 5060 of the laptop upon which Ekiga is running? > > At the moment, there are no port forwarding rules in place. Hi Colin, which router do you use? Just wondering that some routers do some kind of 6050 mapping automatically and you can\'t see it in port forwarding options, Speedtouch 510/530 being a well known example... If this is not the case, perhaps you can try to forward 6050 to your notebook (this is just a blind attempt, of course, as the opposite helped in my case - but still may be worth a shot since we have reasons to believe that Kamailio has problems with your current NAT settings) Palo > > Until next time, Colin. > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > __________ Najoriginalnejsie technologicke hracky - http://pocitace.sme.sk/ From f.vonbock at gmail.com Mon Dec 15 08:47:15 2008 From: f.vonbock at gmail.com (Fedor vonBock) Date: Mon, 15 Dec 2008 11:47:15 +0300 Subject: [Ekiga-list] request timeout ekiga 3.0.0 ubuntu hardy Message-ID: I thought i'd keep this in its own since the log message is not too short. This is the output after running "ekiga -d 4" on the terminal to interface 0 - "192.168.1.67%eth0" 2008/12/13 18:50:40.580 0:12.010 subscriber:0xb357ab90 SIP Transaction created. 2008/12/13 18:50:40.583 0:12.013 subscriber:0xb357ab90 DNS SRV Lookup sip.diamondcard.us service _sip._udp 2008/12/13 18:50:41.602 0:13.032 Housekeeper:0xb5878b90 SIP Set state Terminated_Timeout for transaction 1 REGISTER 2008/12/13 18:50:41.602 0:13.032 Housekeeper:0xb5878b90 SIP Changing REGISTER handler from Subscribing to Unavailable, target= sip:alikhalfan1 at ekiga.net , id=0e35fd72-9bc7-dd11-8a6f-001cc0223352 at khalfan-desktop 2008/12/13 18:50:41.602 0:13.032 Housekeeper:0xb5878b90 SIP Retrying REGISTER in 30 seconds. 2008/12/13 18:50:45.870 0:17.300 subscriber:0xb357ab90 SIP Transaction remote address is udp$62.4.81.186:5060 2008/12/13 18:50:45.871 0:17.301 subscriber:0xb357ab90 SIP Sending PDU (549 bytes) to: rem=udp$62.4.81.186:5060,local=udp$ 84.255.181.235:5060,if=192.168.1.67%eth0 REGISTER sip:sip.diamondcard.us SIP/2.0 CSeq: 2 REGISTER Via: SIP/2.0/UDP 84.255.181.235:5060 ;branch=z9hG4bK724e1376-9bc7-dd11-8a6f-001cc0223352;rport User-Agent: Ekiga/3.0.0 From: >;tag=5a481376-9bc7-dd11-8a6f-001cc0223352 Call-ID: c479fd72-9bc7-dd11-8a6f-001cc0223352 at khalfan-desktop To: > Contact: Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 3600 Content-Length: 0 Max-Forwards: 70 2008/12/13 18:50:45.871 0:17.301 subscriber:0xb357ab90 SIP Transaction timers set: retry=0.500, completion=6.000 2008/12/13 18:50:45.871 0:17.301 ThreadID:0xb357ab90 PWLib Destroyed thread 0x83751e0 subscriber:0xb357ab90(id = 0) 2008/12/13 18:50:46.371 0:17.801 Housekeeper:0xb5878b90 SIP Transaction 2 REGISTER timeout, making retry 1 2008/12/13 18:50:46.371 0:17.801 Housekeeper:0xb5878b90 OpalUDP Setting interface to 192.168.1.67%eth0 2008/12/13 18:50:46.372 0:17.802 Housekeeper:0xb5878b90 SIP Sending PDU (549 bytes) to: rem=udp$62.4.81.186:5060,local=udp$ 84.255.181.235:5060,if=192.168.1.67%eth0 REGISTER sip:sip.diamondcard.us SIP/2.0 CSeq: 2 REGISTER Via: SIP/2.0/UDP 84.255.181.235:5060 ;branch=z9hG4bK724e1376-9bc7-dd11-8a6f-001cc0223352;rport User-Agent: Ekiga/3.0.0 From: >;tag=5a481376-9bc7-dd11-8a6f-001cc0223352 Call-ID: c479fd72-9bc7-dd11-8a6f-001cc0223352 at khalfan-desktop To: > Contact: Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 3600 Content-Length: 0 Max-Forwards: 70 2008/12/13 18:50:46.372 0:17.802 Housekeeper:0xb5878b90 OpalUDP Setting interface to 192.168.1.67%eth0 2008/12/13 18:50:46.871 0:18.301 Opal Garbage:0xb58fab90 SIP Transaction 1 REGISTER destroyed. 2008/12/13 18:50:47.372 0:18.802 Housekeeper:0xb5878b90 SIP Transaction 2 REGISTER timeout, making retry 2 2008/12/13 18:50:47.372 0:18.802 Housekeeper:0xb5878b90 OpalUDP Setting interface to 192.168.1.67%eth0 2008/12/13 18:50:47.372 0:18.802 Housekeeper:0xb5878b90 SIP Sending PDU (549 bytes) to: rem=udp$62.4.81.186:5060,local=udp$ 84.255.181.235:5060,if=192.168.1.67%eth0 REGISTER sip:sip.diamondcard.us SIP/2.0 CSeq: 2 REGISTER Via: SIP/2.0/UDP 84.255.181.235:5060 ;branch=z9hG4bK724e1376-9bc7-dd11-8a6f-001cc0223352;rport User-Agent: Ekiga/3.0.0 From: >;tag=5a481376-9bc7-dd11-8a6f-001cc0223352 Call-ID: c479fd72-9bc7-dd11-8a6f-001cc0223352 at khalfan-desktop To: > Contact: Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 3600 Content-Length: 0 Max-Forwards: 70 2008/12/13 18:50:47.372 0:18.802 Housekeeper:0xb5878b90 OpalUDP Setting interface to 192.168.1.67%eth0 2008/12/13 18:50:49.372 0:20.802 Housekeeper:0xb5878b90 SIP Transaction 2 REGISTER timeout, making retry 3 2008/12/13 18:50:49.372 0:20.802 Housekeeper:0xb5878b90 OpalUDP Setting interface to 192.168.1.67%eth0 2008/12/13 18:50:49.372 0:20.802 Housekeeper:0xb5878b90 SIP Sending PDU (549 bytes) to: rem=udp$62.4.81.186:5060,local=udp$ 84.255.181.235:5060,if=192.168.1.67%eth0 REGISTER sip:sip.diamondcard.us SIP/2.0 CSeq: 2 REGISTER Via: SIP/2.0/UDP 84.255.181.235:5060 ;branch=z9hG4bK724e1376-9bc7-dd11-8a6f-001cc0223352;rport User-Agent: Ekiga/3.0.0 From: >;tag=5a481376-9bc7-dd11-8a6f-001cc0223352 Call-ID: c479fd72-9bc7-dd11-8a6f-001cc0223352 at khalfan-desktop To: > Contact: Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 3600 Content-Length: 0 Max-Forwards: 70 2008/12/13 18:50:49.372 0:20.802 Housekeeper:0xb5878b90 OpalUDP Setting interface to 192.168.1.67%eth0 2008/12/13 18:50:51.872 0:23.302 Housekeeper:0xb5878b90 SIP Set state Terminated_Timeout for transaction 2 REGISTER 2008/12/13 18:50:51.872 0:23.302 Housekeeper:0xb5878b90 SIP Changing REGISTER handler from Subscribing to Unavailable, target= sip:324278 at sip.diamondcard.us , id=c479fd72-9bc7-dd11-8a6f-001cc0223352 at khalfan-desktop 2008/12/13 18:50:51.872 0:23.302 Housekeeper:0xb5878b90 SIP Retrying REGISTER in 30 seconds. 2008/12/13 18:50:51.872 0:23.302 Opal Garbage:0xb58fab90 SIP Transaction 2 REGISTER destroyed. -------------- next part -------------- An HTML attachment was scrubbed... URL: From dsandras at seconix.com Mon Dec 15 20:38:32 2008 From: dsandras at seconix.com (Damien Sandras) Date: Mon, 15 Dec 2008 21:38:32 +0100 Subject: [Ekiga-list] \"remote user cleared the call\" problem In-Reply-To: <49418C42.000001.15677@kamasutra> References: <49418C42.000001.15677@kamasutra> Message-ID: <1229373512.13601.41.camel@scorpion.multitel.be> Le jeudi 11 d?cembre 2008 ? 22:55 +0100, Palo S. a ?crit : > > > > Not sure how to fix Kamailio > > It may be possible for Kamailio developers to > identify place (in the code) where Kamailio > sends this CANCEL by itself and fix... > > > but I wonder if the CANCEL is not taken > > into account when it should not be. > > I think that Ekiga does it correctly, at least > I can\'t see why should it not take it into > account. If there is a safe way to distinguish > between \"correct\" and \"incorrect\" CANCEL then > of course, however I don\'t know how that could > be done Some of the CANCEL's (due to forking) should have been ignored and they were not. A fix has been put into the stable branch and into TRUNK. Is that something you can test ? -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From dsandras at seconix.com Mon Dec 15 20:39:42 2008 From: dsandras at seconix.com (Damien Sandras) Date: Mon, 15 Dec 2008 21:39:42 +0100 Subject: [Ekiga-list] could not register : behind a router In-Reply-To: References: <380681.85679.qm@web38303.mail.mud.yahoo.com> Message-ID: <1229373582.13601.45.camel@scorpion.multitel.be> Le samedi 13 d?cembre 2008 ? 18:53 +0300, Fedor vonBock a ?crit : > ok, > I run ekiga with parameter -d 4 to capture the message and this is > what i got (last lines) Is it better if you disable STUN support ? Or from the log, wouldn't you be using IP Translation ? -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From phil-ekiga at tinsleyviaduct.com Mon Dec 15 22:55:08 2008 From: phil-ekiga at tinsleyviaduct.com (Phil Reynolds) Date: Mon, 15 Dec 2008 22:55:08 +0000 Subject: [Ekiga-list] h263 in Debian lenny / bare number dial In-Reply-To: <49455D77.6080600@pu-pm.univ-fcomte.fr> References: <20081211231012.18782i2xw8099uxg@topdeck.tinsleyviaduct.com> <4943A3D3.7020704@pu-pm.univ-fcomte.fr> <20081213144245.15721gn47n4rbo4l@topdeck.tinsleyviaduct.com> <4943CC21.8070804@pu-pm.univ-fcomte.fr> <20081213184352.8335370fiojfxeg8@topdeck.tinsleyviaduct.com> <49455D77.6080600@pu-pm.univ-fcomte.fr> Message-ID: <20081215225508.16290oz1zgot8sp8@topdeck.tinsleyviaduct.com> Quoting "Eugen Dedu" : > Phil Reynolds wrote: >> Quoting "Eugen Dedu" : >> >>> Phil Reynolds wrote: >>>> Quoting "Eugen Dedu" : >>>> >>>>> Hi, >>>>> >>>>> Phil Reynolds wrote: >>>>>> I am trying to get ekiga to work in Debian lenny, with the H263 >>>>>> codec, but when I build opal, H263 is not supported. I am >>>>>> currently backporting packages from experimental. >>>>>> >>>>>> What do I need to do to get h263? Is there a better way to do >>>>>> this, remaining otherwise on lenny? >>>>> >>>>> You must install libavcodec-dev not from debian (h263 is not >>>>> dfsg), but from other site, for ex. http://debian-multimedia.org. >>>> >>>> It seems that ptlib wants libdc1394-13-dev and libavcodec-dev >>>> installs -22-dev - these are conflicting requirements that in >>>> turn cause there to be no h263. >>> >>> Indeed (http://bugzilla.gnome.org/show_bug.cgi?id=545017). I >>> always compile ptlib with libdc1394-13-dev, and install -22-dev >>> right before compiling opal. >> >> Still no h263 here even when I do that. > > Please send the output of configure of opal. Here's what it shows. I only get H.261 and theora: #don't build h263-ffmpeg codec because it uses an unmaintained binary ./configure --build x86_64-linux-gnu --prefix=/usr --disable-ffmpeg-h263 checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for g++... g++ checking for C++ compiler default output file name... a.out checking whether the C++ compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking for gcc... gcc checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for a BSD-compatible install... /usr/bin/install -c checking for ranlib... ranlib checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for ar... ar configure: gcc version is 4.3.2 checking if gcc version is valid... yes checking for working bit scan intrinsic... yes configure: Opal version is 3.4.2 checking where plugins are being installed... /usr/lib/opal-3.4.2 checking wether to build a shared library... yes checking build system type... x86_64-pc-linux-gnu checking host system type... x86_64-pc-linux-gnu checking target system type... x86_64-pc-linux-gnu checking Debugging support... no checking for PTLIB... yes Version: 2.4.2 CFLAGS: -DPTRACING=1 -D_REENTRANT -D_GNU_SOURCE=1 -fno-exceptions -I/usr/inclu de/SDL CXXFLAGS: -felide-constructors -Wreorder DEBUG: -lpt_d -lpthread -lsasl2 -lldap -llber -lldap_r -lssl -lcrypto -lexpat -lSDL -lodbc -lresolv -ldl RELEASE: -lpt -lpthread -lsasl2 -lldap -llber -lldap_r -lssl -lcrypto -lexpat - lSDL -lodbc -lresolv -ldl checking ptlib version... 2.4.2 checking PTLIB has SSL... yes checking PTLIB has ASN.1... yes checking PTLIB has expat... yes checking PTLIB has video... yes checking PTLIB has wavfile... yes checking PTLIB has vxml... yes checking PTLIB has ipv6... yes checking PTLIB has dtmf... yes checking PTLIB has ldap... yes checking PTLIB has dns... yes checking PTLIB has audio... yes checking PTLIB has config... yes checking PTLIB has option ssl/aes... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking how to run the C++ preprocessor... g++ -E checking dlfcn.h usability... yes checking dlfcn.h presence... yes checking for dlfcn.h... yes checking if dlopen is available... yes checking for dlopen in -ldl... yes checking for short... yes checking size of short... 2 checking for int... yes checking size of int... 4 checking for long... yes checking size of long... 8 checking for long long... yes checking size of long long... 8 checking for SPEEXDSP... yes checking speex/speex.h usability... yes checking speex/speex.h presence... yes checking for speex/speex.h... yes checking for speex/speex.h... (cached) yes checking Speex has float... no checking ZRTP protocol support... no checking libsrtp support... no checking jni.h usability... no checking jni.h presence... no checking for jni.h... no checking whether to enable video codec support... yes checking whether to enable SIP protocol support... yes checking whether to enable H.323 protocol support... yes checking whether to enable IAX2 protocol support... yes checking whether to enable H.224 protocol support... yes checking whether to enable T.38 capability support... yes checking whether to enable T.38 FAX protocol support... yes checking whether to enable H.450... yes checking whether to enable H.460... yes checking whether to enable LID support... yes checking whether to enable IVR support... yes checking whether to enable RFC4175 support... yes checking whether to enable accoustic echo cancellation support... yes checking whether to enable Packet Loss Concealment for G.711... yes checking whether to enable statistics gathering support... yes checking whether to enable plugin support... yes checking whether to enable samples build... no configure: creating ./config.status config.status: creating opal_defs.mak config.status: creating Makefile config.status: creating opal.pc config.status: creating opal.spec config.status: creating opal_cfg.dxy config.status: creating src/codec/speex/libspeex/speex_config_types.h config.status: creating include/opal/buildopts.h === configuring in plugins (/scratch/opal-3.4.2~dfsg/plugins) configure: running /bin/sh ./configure '--prefix=/usr' '--build' 'x86_64-linux- gnu' '--disable-ffmpeg-h263' 'build_alias=x86_64-linux-gnu' 'CXXFLAGS=-g -O2' 'L DFLAGS= -Wl,-z,def' 'CPPFLAGS=' 'CFLAGS=-Wall -g -O2' --cache-file=/dev/null --s rcdir=. checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking build system type... x86_64-pc-linux-gnu checking host system type... x86_64-pc-linux-gnu checking target system type... x86_64-pc-linux-gnu checking Debugging support... no checking for g++... g++ checking for C++ compiler default output file name... a.out checking whether the C++ compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking for gcc... gcc checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for a BSD-compatible install... /usr/bin/install -c checking for ranlib... ranlib checking for nm... nm checking for ldd... ldd checking for objdump... objdump checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking stddef.h usability... yes checking stddef.h presence... yes checking for stddef.h... yes checking limits.h usability... yes checking limits.h presence... yes checking for limits.h... yes checking float.h usability... yes checking float.h presence... yes checking for float.h... yes checking fcntl.h usability... yes checking fcntl.h presence... yes checking for fcntl.h... yes checking OPAL Version... 3.4.2 checking Plugin install directory... /usr/lib/opal-3.4.2 checking sys/time.h usability... yes checking sys/time.h presence... yes checking for sys/time.h... yes checking sys/file.h usability... yes checking sys/file.h presence... yes checking for sys/file.h... yes checking netinet/in.h usability... yes checking netinet/in.h presence... yes checking for netinet/in.h... yes checking vfork.h usability... no checking vfork.h presence... no checking for vfork.h... no checking for fork... yes checking for vfork... yes checking for working fork... yes checking for working vfork... (cached) yes checking for gsm_create in -lgsm... yes checking if system GSM library has WAV49... yes checking System GSM... yes using system GSM checking for short... yes checking size of short... 2 checking for int... yes checking size of int... 4 checking for long... yes checking size of long... 8 checking for long long... yes checking size of long long... 8 checking internal Speex version... 1.1.11.1 configure: checking whether system Speex or internal Speex is more recent checking for SPEEX... yes using system Speex version 1.2rc1 checking enable plugin supporting H.263 via patched FFMPEG... no checking default to full capabilities at empty fmtp lines... yes checking for LIBAVCODEC... yes configure: libavcodec stack align hack disabled checking filename of libavcodec library... conftest.c: In function 'main': conftest.c:1: warning: control reaches end of non-void function libavcodec.so.51 checking if libavcodec has h263p_encoder... conftest.c: In function 'main': conftest.c:1: warning: control reaches end of non-void function yes checking if libavcodec has mpeg4_encoder... conftest.c: In function 'main': conftest.c:1: warning: control reaches end of non-void function yes checking if libavcodec has h264_decoder... conftest.c: In function 'main': conftest.c:1: warning: control reaches end of non-void function yes checking libavcodec/avcodec.h usability... yes checking libavcodec/avcodec.h presence... no configure: WARNING: libavcodec/avcodec.h: accepted by the compiler, rejected by the preprocessor! configure: WARNING: libavcodec/avcodec.h: proceeding with the compiler's result checking for libavcodec/avcodec.h... yes checking libavcodec source... disabled checking for X264... yes checking filename of libx264 library... conftest.c: In function 'main': conftest.c:1: warning: control reaches end of non-void function libx264.so.60 configure: x264 static linking disabled checking for THEORA... yes checking dlfcn.h usability... yes checking dlfcn.h presence... yes checking for dlfcn.h... yes checking if dlopen is available... yes checking for dlopen in -ldl... yes checking enable H.264 support... yes checking IXJ... no checking enable voicetronix vpb... yes checking capi20.h usability... no checking capi20.h presence... no checking for capi20.h... no checking CAPI... no checking for t38_indicator in -lspandsp... no configure: creating ./config.status config.status: creating audio/GSM0610/Makefile config.status: creating audio/gsm-amr/Makefile config.status: creating audio/Speex/Makefile config.status: creating audio/LPC_10/Makefile config.status: creating audio/G726/Makefile config.status: creating audio/IMA_ADPCM/Makefile config.status: creating video/H.261-vic/Makefile config.status: creating video/H.263-ffmpeg/Makefile config.status: creating video/H.263-1998/Makefile config.status: creating video/MPEG4-ffmpeg/Makefile config.status: creating video/H.264/Makefile config.status: creating video/H.264/gpl/Makefile config.status: creating video/THEORA/Makefile config.status: creating LID/IxJ/Makefile config.status: creating LID/VPB/Makefile config.status: creating LID/CAPI/Makefile config.status: creating fax/fax_spandsp/Makefile config.status: creating Makefile config.status: creating audio/Speex/libspeex/speex_config_types.h configure: creating ./config.status config.status: creating audio/GSM0610/Makefile config.status: creating audio/gsm-amr/Makefile config.status: creating audio/Speex/Makefile config.status: creating audio/LPC_10/Makefile config.status: creating audio/G726/Makefile config.status: creating audio/IMA_ADPCM/Makefile config.status: creating video/H.261-vic/Makefile config.status: creating video/H.263-ffmpeg/Makefile config.status: creating video/H.263-1998/Makefile config.status: creating video/MPEG4-ffmpeg/Makefile config.status: creating video/H.264/Makefile config.status: creating video/H.264/gpl/Makefile config.status: creating video/THEORA/Makefile config.status: creating LID/IxJ/Makefile config.status: creating LID/VPB/Makefile config.status: creating LID/CAPI/Makefile config.status: creating fax/fax_spandsp/Makefile config.status: creating Makefile config.status: creating audio/Speex/libspeex/speex_config_types.h config.status: creating plugin-config.h =================== Plugin configuration ====================== prefix : /usr exec_prefix : ${prefix} libdir : ${exec_prefix}/lib Audio Codec plugin install dir : ${libdir}/opal-3.4.2/codecs/audio Video Codec plugin install prefix: ${libdir}/opal-3.4.2/codecs/video LID plugin install prefix : ${libdir}/opal-3.4.2/lid FAX plugin install prefix : ${libdir}/opal-3.4.2/fax GSM : yes (system) gsm-amr : yes iLBC : yes Speex : yes (system, version 1.2rc1) LPC10 : yes G.726 : yes IMA_ADPCM : yes H.261 : yes H.263 : no H.263+ : yes H.264 : yes THEORA : yes MPEG4 Part 2 : yes (no rate control correction) SpanDSP FAX : no CAPI : no Quicknet xJACK support : no Voicetronics VPB support : yes OS Type : linux-gnu Machine Type : x86_64 If all settings are OK, type make and make install ======================================================== -- Phil Reynolds mail: phil-ekiga at tinsleyviaduct.com Web: http://www.tinsleyviaduct.com/phil/ Waltham 66, Emley Moor 69, Droitwich 79, Windows 95 ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. From f.vonbock at gmail.com Tue Dec 16 07:20:55 2008 From: f.vonbock at gmail.com (Fedor vonBock) Date: Tue, 16 Dec 2008 10:20:55 +0300 Subject: [Ekiga-list] could not register : behind a router In-Reply-To: <1229373582.13601.45.camel@scorpion.multitel.be> References: <380681.85679.qm@web38303.mail.mud.yahoo.com> <1229373582.13601.45.camel@scorpion.multitel.be> Message-ID: could this be a problem with opal? On Mon, Dec 15, 2008 at 11:39 PM, Damien Sandras wrote: > Le samedi 13 d?cembre 2008 ? 18:53 +0300, Fedor vonBock a ?crit : > > ok, > > I run ekiga with parameter -d 4 to capture the message and this is > > what i got (last lines) > > > Is it better if you disable STUN support ? > > Or from the log, wouldn't you be using IP Translation ? > -- > _ Damien Sandras > (o- > //\ Ekiga Softphone : http://www.ekiga.org/ > v_/_ Be IP : http://www.beip.be/ > FOSDEM : http://www.fosdem.org/ > SIP Phone : sip:dsandras at ekiga.net > > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dsandras at seconix.com Tue Dec 16 08:05:03 2008 From: dsandras at seconix.com (Damien Sandras) Date: Tue, 16 Dec 2008 09:05:03 +0100 Subject: [Ekiga-list] could not register : behind a router In-Reply-To: References: <380681.85679.qm@web38303.mail.mud.yahoo.com> <1229373582.13601.45.camel@scorpion.multitel.be> Message-ID: <1229414703.13601.53.camel@scorpion.multitel.be> Le mardi 16 d?cembre 2008 ? 10:20 +0300, Fedor vonBock a ?crit : > could this be a problem with opal? No, it is a problem with your setup. Can you answer my two questions about it ? 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:dsandras at ekiga.net From michel.memeteau at gmail.com Tue Dec 16 11:02:48 2008 From: michel.memeteau at gmail.com (michel memeteau) Date: Tue, 16 Dec 2008 12:02:48 +0100 Subject: [Ekiga-list] Sip with new firmware on french LiveBox Message-ID: Hi , this message i more towards the LiveBox users in france. I 've read that since last august, Orange ADSL now use SIP for its VOIP, and this conflict with using a SIP client behind a LiveBOx http://forum.mandriva.com/viewtopic.php?p=608205#608205 Can anyone confirm this ? this is a common problems when ISP use SIP and don't care that their clients won't be able to use it with the modem supplied. This would make sense for orange who wants to be sure that you will use their voip and not some voipbuster -- %<------------------------------------------------------->% Michel memeteau Blog 0.2 : http://memeteau.free.fr Fixe : 0974763294 Mobile : 0624808051 VOIP | Visio: sip:freechelmi at ippi.fr jabber/GTalk : xmpp:freechelmi at jabber.fr -------------- next part -------------- An HTML attachment was scrubbed... URL: From andre at bwh.harvard.edu Tue Dec 16 23:27:22 2008 From: andre at bwh.harvard.edu (Andre Robatino) Date: Tue, 16 Dec 2008 18:27:22 -0500 Subject: [Ekiga-list] port triggering rule in symmetric NAT router no longer works with Ekiga 3 Message-ID: <4948395A.9070702@bwh.harvard.edu> My father has a symmetric NAT router, and when he was using Ekiga 2, we put a port triggering rule in his router which would trigger on port 3478 and open ports 5000-5100, as described in http://wiki.ekiga.org/index.php/Ekiga_behind_a_NAT_router This allowed the Configuration Druid to see his router as Port Restricted NAT, and he could receive incoming calls (although for some reason, there was a roughly 3-minute delay after a call before incoming calls could get through). Now he's using Ekiga 3, and whenever it starts, it says that Ekiga did not manage to configure the network automatically, so it has to be done manually, according to http://wiki.ekiga.org/index.php/Enable_port_forwarding_manually My question is, why doesn't the port triggering rule suffice any more? -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3266 bytes Desc: S/MIME Cryptographic Signature URL: From palos at post.sk Wed Dec 17 00:49:44 2008 From: palos at post.sk (Palo S.) Date: 17 Dec 2008 01:49:44 +0100 (CET) Subject: [Ekiga-list] \"remote user cleared the call\" problem Message-ID: <49484CA8.000003.27899@kamasutra> > > Some of the CANCEL\'s (due to forking) should have been ignored and they > were not. > > A fix has been put into the stable branch and into TRUNK. Is that > something you can test ? 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:dsandras at ekiga.net > > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list __________ http://kultura.sme.sk/ - Informa?n? server o kult?re a ?oubiznise From f.vonbock at gmail.com Wed Dec 17 14:01:30 2008 From: f.vonbock at gmail.com (Ali) Date: Wed, 17 Dec 2008 17:01:30 +0300 Subject: [Ekiga-list] could not register : behind a router In-Reply-To: <1229414703.13601.53.camel@scorpion.multitel.be> References: <380681.85679.qm@web38303.mail.mud.yahoo.com> <1229373582.13601.45.camel@scorpion.multitel.be> <1229414703.13601.53.camel@scorpion.multitel.be> Message-ID: <4949063A.6070809@gmail.com> Damien Sandras wrote: > Le mardi 16 d?cembre 2008 ? 10:20 +0300, Fedor vonBock a ?crit : > >> could this be a problem with opal? >> > > No, it is a problem with your setup. Can you answer my two questions > about it ? > > Thanks, > > Enabling or disabling STUN doesn't make a difference at all. I was able to ring my phone using Twinkle without stun, as for ip translation, i don't think there is any (not sure) the 192.168.1.1 is my router address. Thanks From Eugen.Dedu at pu-pm.univ-fcomte.fr Wed Dec 17 15:30:13 2008 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Wed, 17 Dec 2008 16:30:13 +0100 Subject: [Ekiga-list] Re^2: file and format of address book In-Reply-To: References: Message-ID: <49491B05.7060509@pu-pm.univ-fcomte.fr> peasthope at shaw.ca wrote: > Eugen & others, > >> Start gconf-editor (which looks into ~/.gconf), ... > > gconf-editor installed under xfce4 and > appears to work. > >> ... choose apps/ekiga/contacts. > > Interesting. According to gconf-editor > contacts appears as a directory but ls > doesn't mention it. > >> You can copy/paste from the old to the new. > > Under "Local Contacts" in the address-book > window in Ekiga, I can create a new address > book named test for example. But then > gconf-editor still shows only one line > beginning "remote_addressbooks_list". Neither > of the address books under "Local Contacts" is > visible. > > Why are Local and Remote contacts distinguished? > Is the distinction only for user understanding? > Is there a technical distinction for the software? Hi, I don't know what to say. You should try ekiga 3, maybe the format for local/remote contacts has changed. -- Eugen From Eugen.Dedu at pu-pm.univ-fcomte.fr Wed Dec 17 15:49:29 2008 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Wed, 17 Dec 2008 16:49:29 +0100 Subject: [Ekiga-list] failure in registration of sip account In-Reply-To: References: Message-ID: <49491F89.8080701@pu-pm.univ-fcomte.fr> peasthope at shaw.ca wrote: > Folk, > > This is Ekiga 2.0.12 in Debian Linuz. > > More often than not, my ekiga.net sip account > fails to register automatically when the client > initializes. There is never a problem > registering manually in the Edit:Accounts window. > Can anyone offer a solution? Please try ekiga 3 if possible, it is available on debian experimental. -- Eugen From dsandras at seconix.com Wed Dec 17 19:38:52 2008 From: dsandras at seconix.com (Damien Sandras) Date: Wed, 17 Dec 2008 20:38:52 +0100 Subject: [Ekiga-list] port triggering rule in symmetric NAT router no longer works with Ekiga 3 In-Reply-To: <4948395A.9070702@bwh.harvard.edu> References: <4948395A.9070702@bwh.harvard.edu> Message-ID: <1229542732.4276.6.camel@scorpion.multitel.be> Le mardi 16 d?cembre 2008 ? 18:27 -0500, Andre Robatino a ?crit : > My father has a symmetric NAT router, and when he was using Ekiga 2, we > put a port triggering rule in his router which would trigger on port > 3478 and open ports 5000-5100, as described in > > http://wiki.ekiga.org/index.php/Ekiga_behind_a_NAT_router > > This allowed the Configuration Druid to see his router as Port > Restricted NAT, and he could receive incoming calls (although for some > reason, there was a roughly 3-minute delay after a call before incoming > calls could get through). > > Now he's using Ekiga 3, and whenever it starts, it says that Ekiga did > not manage to configure the network automatically, so it has to be done > manually, according to > > http://wiki.ekiga.org/index.php/Enable_port_forwarding_manually > > My question is, why doesn't the port triggering rule suffice any more? That is very weird, because the STUN support and the ports have not changed. Are you sure Ekiga 2.00 still works with the same configuration ? -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From dsandras at seconix.com Wed Dec 17 19:39:22 2008 From: dsandras at seconix.com (Damien Sandras) Date: Wed, 17 Dec 2008 20:39:22 +0100 Subject: [Ekiga-list] could not register : behind a router In-Reply-To: <4949063A.6070809@gmail.com> References: <380681.85679.qm@web38303.mail.mud.yahoo.com> <1229373582.13601.45.camel@scorpion.multitel.be> <1229414703.13601.53.camel@scorpion.multitel.be> <4949063A.6070809@gmail.com> Message-ID: <1229542762.4276.8.camel@scorpion.multitel.be> Le mercredi 17 d?cembre 2008 ? 17:01 +0300, Ali a ?crit : > Damien Sandras wrote: > > Le mardi 16 d?cembre 2008 ? 10:20 +0300, Fedor vonBock a ?crit : > > > >> could this be a problem with opal? > >> > > > > No, it is a problem with your setup. Can you answer my two questions > > about it ? > > > > Thanks, > > > > > > Enabling or disabling STUN doesn't make a difference at all. I was able > to ring my phone using Twinkle without stun, > > as for ip translation, i don't think there is any (not sure) the > 192.168.1.1 is my router address. > As I see it in the trace, I think you enabled IP Translation in Ekiga when doing the tests. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From andre at bwh.harvard.edu Wed Dec 17 21:18:36 2008 From: andre at bwh.harvard.edu (Andre Robatino) Date: Wed, 17 Dec 2008 16:18:36 -0500 Subject: [Ekiga-list] port triggering rule in symmetric NAT router no longer works with Ekiga 3 In-Reply-To: <1229542732.4276.6.camel@scorpion.multitel.be> References: <4948395A.9070702@bwh.harvard.edu> <1229542732.4276.6.camel@scorpion.multitel.be> Message-ID: <49496CAC.5020703@bwh.harvard.edu> Damien Sandras wrote: > Le mardi 16 d?cembre 2008 ? 18:27 -0500, Andre Robatino a ?crit : >> My father has a symmetric NAT router, and when he was using Ekiga 2, we >> put a port triggering rule in his router which would trigger on port >> 3478 and open ports 5000-5100, as described in >> >> http://wiki.ekiga.org/index.php/Ekiga_behind_a_NAT_router >> >> This allowed the Configuration Druid to see his router as Port >> Restricted NAT, and he could receive incoming calls (although for some >> reason, there was a roughly 3-minute delay after a call before incoming >> calls could get through). >> >> Now he's using Ekiga 3, and whenever it starts, it says that Ekiga did >> not manage to configure the network automatically, so it has to be done >> manually, according to >> >> http://wiki.ekiga.org/index.php/Enable_port_forwarding_manually >> >> My question is, why doesn't the port triggering rule suffice any more? > > That is very weird, because the STUN support and the ports have not > changed. Are you sure Ekiga 2.00 still works with the same > configuration ? We both migrated from Fedora 9 (with Ekiga 2.0.12) to Fedora 10 (with Ekiga 3.0.1), so we don't know whether 2.0.12 would have worked. But it's likely, since he never changed the router configuration. We've determined that after starting Ekiga 3, it's impossible for him to make any calls unless he goes through the Configuration Assistant. He doesn't have to change anything, just click through all the screens (including leaving "Keep current settings" in the Connection Type screen). After doing this, he can make Ekiga echo test calls with audio/video working normally, but neither of us can call the other. (I can also make echo test calls normally, so the problem is probably not at my end.) And if Ekiga is restarted, it's necessary for him to go through the Configuration Assistant again just to get back to this state. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3266 bytes Desc: S/MIME Cryptographic Signature URL: From dsandras at seconix.com Wed Dec 17 22:02:49 2008 From: dsandras at seconix.com (Damien Sandras) Date: Wed, 17 Dec 2008 23:02:49 +0100 Subject: [Ekiga-list] port triggering rule in symmetric NAT router no longer works with Ekiga 3 In-Reply-To: <49496CAC.5020703@bwh.harvard.edu> References: <4948395A.9070702@bwh.harvard.edu> <1229542732.4276.6.camel@scorpion.multitel.be> <49496CAC.5020703@bwh.harvard.edu> Message-ID: <1229551369.16049.0.camel@scorpion.multitel.be> Le mercredi 17 d?cembre 2008 ? 16:18 -0500, Andre Robatino a ?crit : > Damien Sandras wrote: > > Le mardi 16 d?cembre 2008 ? 18:27 -0500, Andre Robatino a ?crit : > >> My father has a symmetric NAT router, and when he was using Ekiga 2, we > >> put a port triggering rule in his router which would trigger on port > >> 3478 and open ports 5000-5100, as described in > >> > >> http://wiki.ekiga.org/index.php/Ekiga_behind_a_NAT_router > >> > >> This allowed the Configuration Druid to see his router as Port > >> Restricted NAT, and he could receive incoming calls (although for some > >> reason, there was a roughly 3-minute delay after a call before incoming > >> calls could get through). > >> > >> Now he's using Ekiga 3, and whenever it starts, it says that Ekiga did > >> not manage to configure the network automatically, so it has to be done > >> manually, according to > >> > >> http://wiki.ekiga.org/index.php/Enable_port_forwarding_manually > >> > >> My question is, why doesn't the port triggering rule suffice any more? > > > > That is very weird, because the STUN support and the ports have not > > changed. Are you sure Ekiga 2.00 still works with the same > > configuration ? > > We both migrated from Fedora 9 (with Ekiga 2.0.12) to Fedora 10 (with > Ekiga 3.0.1), so we don't know whether 2.0.12 would have worked. But > it's likely, since he never changed the router configuration. > > We've determined that after starting Ekiga 3, it's impossible for him to > make any calls unless he goes through the Configuration Assistant. He > doesn't have to change anything, just click through all the screens > (including leaving "Keep current settings" in the Connection Type > screen). After doing this, he can make Ekiga echo test calls with > audio/video working normally, but neither of us can call the other. (I > can also make echo test calls normally, so the problem is probably not > at my end.) And if Ekiga is restarted, it's necessary for him to go > through the Configuration Assistant again just to get back to this state. That does not really make sense, except if some settings are lost in between. Can you provide a -d 4 with and without the druid being ran ? -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From fshock at hotmail.com Thu Dec 18 00:39:46 2008 From: fshock at hotmail.com (FS Inc.) Date: Thu, 18 Dec 2008 00:39:46 +0000 Subject: [Ekiga-list] Unable to get incoming calls from sip provider ekiga.net set up on asterisk Message-ID: I've been using the wiki as a guide here... http://wiki.ekiga.org/index.php/Connecting_Asterisk_to_ekiga.net I've also tried various permutations, combinations and contortions but nada. below is my extensions.conf ***** begin extensions.conf **** [general] static = yes writeprotect = no autofallthrough = yes clearglobalvars = no [globals] CONSOLE = Console/dsp ; Console interface for demo ;CONSOLE=Zap/1 ;CONSOLE=Phone/phone0 IAXINFO = guest ; IAXtel username/password ;IAXINFO=myuser:mypass TRUNK = Zap/G2 ; Trunk interface TRUNKMSD = 1 ; MSD digits to strip (usually 1 or 0) ;TRUNK=IAX2/user:pass at provider [default] exten => s,1,Verbose(1|Unrouted call handler) exten => s,n,Answer() exten => s,n,Wait(1) exten => s,n,Playback(tt-weasels) exten => s,n,Hangup() [macro-voicemail] exten => s,1,Dial(${ARG1},20) exten => s,n,Goto(s-${DIALSTATUS},1) exten => s-NOANSWER,1,Voicemail(u${MACRO_EXTEN}) exten => s-NOANSWER,n,Hangup() exten => s-BUSY,1,Voicemail(b${MACRO_EXTEN}) exten => s-BUSY,n,Hangup() exten => _s-.,1,Goto(s-NOANSWER,1) [incoming_calls] exten => ekiga_meyamma_in,1,Macro(voicemail,SIP/101) exten => ekiga_meyamma_in,n,Hangup() [internal_calls] exten => 101,1,Macro(voicemail,SIP/101) exten => 101,n,Hangup() exten => 102,1,Dial(SIP/102) exten => 102,n,Hangup() exten => 8,1,VoiceMailMain(s${CALLERIDNUM}) exten => 8,n,Hangup() exten => 600,1,Answer() exten => 600,n,Playback(demo-echotest) exten => 600,n,Echo() exten => 600,n,Playback(demo-echodone) exten => 600,n,Hangup() [outgoing_calls] exten => _9.,1,Dial(SIP/ekiga_meyamma_out/${EXTEN:1},20,r)) exten => _9.,n,Hangup() [home] include => internal_calls include => outgoing_calls ***** end extensions.conf **** below is my sip.conf **** begin sip.conf *** [general] context=default bindport=5060 bindaddr=0.0.0.0 srvlookup=yes disallow=all allow=ulaw allow=alaw allow=ilbc allow=gsm allow=h261 videosupport=yes ; Register 2345 at sip provider 'sip_proxy'. Calls from this provider ; connect to local extension 1234 in extensions.conf, default context, ; unless you configure a [sip_proxy] section below, and configure a ; context. ; Tip 1: Avoid assigning hostname to a sip.conf section like [provider.com] ; Tip 2: Use separate type=peer and type=user sections for SIP providers ; (instead of type=friend) if you have calls in both directions register => meyamma:meyamma at ekiga.net/ekiga_meyamma_in externhost=fspublic.selfip.com externrefresh=10 ; localnet=192.168.1.0/255.255.255.0 [authentication] ;setup [101] type=friend username=101 secret=welcome qualify=yes nat=no host=dynamic canreinvite=no context=home ;port=5061 ;setup [102] type=friend username=102 secret=welcome qualify=yes nat=no host=dynamic canreinvite=no context=home ;port=5061 ;ekiga.net [ekiga_meyamma_out] type=peer username=meyamma secret=meyamma host=ekiga.net canreinvite=no qualify=300 insecure=port,invite ;ekiga.net [ekiga_meyamma_in] type=user username=meyamma secret=meyamma host=ekiga.net canreinvite=no qualify=300 context=incoming_calls insecure=port,invite **** end sip.conf **** These are the latest incantations of my sip and extensions conf files. Can anyone assist in helping me to get incoming calls from ekiga.net set up. I have the outgoing working as that was the simple part. That one is handled by [ekiga_meyamma_out] and [outgoing_calls]. Thanks a mil _________________________________________________________________ Explore the seven wonders of the world http://search.msn.com/results.aspx?q=7+wonders+world&mkt=en-US&form=QBRE -------------- next part -------------- An HTML attachment was scrubbed... URL: From archna.mittal at globallogic.com Thu Dec 18 06:25:52 2008 From: archna.mittal at globallogic.com (Archna Mittal) Date: Thu, 18 Dec 2008 11:55:52 +0530 Subject: [Ekiga-list] LDAP Support in Ekiga Windows Version 3.0.0 Message-ID: <30A7EEA43B6F2F4285A916732F994B69B04CAD@ex2-del1.synapse.com> 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. If this integration is not feasible, any other pointers about freeware SIP softphone who supports LDAP integration are highly appreciated. Thanks in Advance, Regards, -Archna -------------- next part -------------- An HTML attachment was scrubbed... URL: From f.vonbock at gmail.com Thu Dec 18 12:43:20 2008 From: f.vonbock at gmail.com (Fedor vonBock) Date: Thu, 18 Dec 2008 15:43:20 +0300 Subject: [Ekiga-list] could not register : behind a router In-Reply-To: <1229542762.4276.8.camel@scorpion.multitel.be> References: <380681.85679.qm@web38303.mail.mud.yahoo.com> <1229373582.13601.45.camel@scorpion.multitel.be> <1229414703.13601.53.camel@scorpion.multitel.be> <4949063A.6070809@gmail.com> <1229542762.4276.8.camel@scorpion.multitel.be> Message-ID: How do i disable it? On Wed, Dec 17, 2008 at 10:39 PM, Damien Sandras wrote: > Le mercredi 17 d?cembre 2008 ? 17:01 +0300, Ali a ?crit : > > Damien Sandras wrote: > > > Le mardi 16 d?cembre 2008 ? 10:20 +0300, Fedor vonBock a ?crit : > > > > > >> could this be a problem with opal? > > >> > > > > > > No, it is a problem with your setup. Can you answer my two questions > > > about it ? > > > > > > Thanks, > > > > > > > > > > Enabling or disabling STUN doesn't make a difference at all. I was able > > to ring my phone using Twinkle without stun, > > > > as for ip translation, i don't think there is any (not sure) the > > 192.168.1.1 is my router address. > > > > As I see it in the trace, I think you enabled IP Translation in Ekiga > when doing the tests. > -- > _ Damien Sandras > (o- > //\ Ekiga Softphone : http://www.ekiga.org/ > v_/_ Be IP : http://www.beip.be/ > FOSDEM : http://www.fosdem.org/ > SIP Phone : sip:dsandras at ekiga.net > > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mansoorhyder1 at gmail.com Thu Dec 18 15:23:16 2008 From: mansoorhyder1 at gmail.com (Mansoor Hyder) Date: Thu, 18 Dec 2008 16:23:16 +0100 Subject: [Ekiga-list] Need info regarding Ekiga Teleconferencing Message-ID: <7161431b0812180723o2d18075br32f99b369c4fc42d@mail.gmail.com> 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. -- Regards -------------------------- Mansoor Hyder -------------- next part -------------- An HTML attachment was scrubbed... URL: From andre at bwh.harvard.edu Thu Dec 18 17:09:24 2008 From: andre at bwh.harvard.edu (Andre Robatino) Date: Thu, 18 Dec 2008 12:09:24 -0500 Subject: [Ekiga-list] port triggering rule in symmetric NAT router no longer works with Ekiga 3 In-Reply-To: <1229551369.16049.0.camel@scorpion.multitel.be> References: <4948395A.9070702@bwh.harvard.edu> <1229542732.4276.6.camel@scorpion.multitel.be> <49496CAC.5020703@bwh.harvard.edu> <1229551369.16049.0.camel@scorpion.multitel.be> Message-ID: <494A83C4.80208@bwh.harvard.edu> Damien Sandras wrote: > Le mercredi 17 d?cembre 2008 ? 16:18 -0500, Andre Robatino a ?crit : >> Damien Sandras wrote: >>> Le mardi 16 d?cembre 2008 ? 18:27 -0500, Andre Robatino a ?crit : >>>> My father has a symmetric NAT router, and when he was using Ekiga 2, we >>>> put a port triggering rule in his router which would trigger on port >>>> 3478 and open ports 5000-5100, as described in >>>> >>>> http://wiki.ekiga.org/index.php/Ekiga_behind_a_NAT_router >>>> >>>> This allowed the Configuration Druid to see his router as Port >>>> Restricted NAT, and he could receive incoming calls (although for some >>>> reason, there was a roughly 3-minute delay after a call before incoming >>>> calls could get through). >>>> >>>> Now he's using Ekiga 3, and whenever it starts, it says that Ekiga did >>>> not manage to configure the network automatically, so it has to be done >>>> manually, according to >>>> >>>> http://wiki.ekiga.org/index.php/Enable_port_forwarding_manually >>>> >>>> My question is, why doesn't the port triggering rule suffice any more? >>> That is very weird, because the STUN support and the ports have not >>> changed. Are you sure Ekiga 2.00 still works with the same >>> configuration ? >> We both migrated from Fedora 9 (with Ekiga 2.0.12) to Fedora 10 (with >> Ekiga 3.0.1), so we don't know whether 2.0.12 would have worked. But >> it's likely, since he never changed the router configuration. >> >> We've determined that after starting Ekiga 3, it's impossible for him to >> make any calls unless he goes through the Configuration Assistant. He >> doesn't have to change anything, just click through all the screens >> (including leaving "Keep current settings" in the Connection Type >> screen). After doing this, he can make Ekiga echo test calls with >> audio/video working normally, but neither of us can call the other. (I >> can also make echo test calls normally, so the problem is probably not >> at my end.) And if Ekiga is restarted, it's necessary for him to go >> through the Configuration Assistant again just to get back to this state. > > That does not really make sense, except if some settings are lost in > between. > > Can you provide a -d 4 with and without the druid being ran ? Today we tried to reproduce the problem and couldn't - even though Ekiga gave the same error message when starting up, when he made the echo test call, it worked even without going through the Configuration Assistant. We are still unable to make calls to each other, even though each of us can make echo test calls. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3266 bytes Desc: S/MIME Cryptographic Signature URL: From andre at bwh.harvard.edu Thu Dec 18 19:46:05 2008 From: andre at bwh.harvard.edu (Andre Robatino) Date: Thu, 18 Dec 2008 14:46:05 -0500 Subject: [Ekiga-list] port triggering rule in symmetric NAT router no longer works with Ekiga 3 In-Reply-To: <494A83C4.80208@bwh.harvard.edu> References: <4948395A.9070702@bwh.harvard.edu> <1229542732.4276.6.camel@scorpion.multitel.be> <49496CAC.5020703@bwh.harvard.edu> <1229551369.16049.0.camel@scorpion.multitel.be> <494A83C4.80208@bwh.harvard.edu> Message-ID: <494AA87D.6000804@bwh.harvard.edu> Andre Robatino wrote: > Today we tried to reproduce the problem and couldn't - even though Ekiga > gave the same error message when starting up, when he made the echo test > call, it worked even without going through the Configuration Assistant. > We are still unable to make calls to each other, even though each of us > can make echo test calls. If he attempts to call me, we are connected for several seconds, then the call disconnects without audio or video ever being established. If I try to call him, it doesn't connect at all. I'm sending you a copy of his output of ekiga -d 4 > output.txt 2>&1 from one of these call attempts by private email. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3266 bytes Desc: S/MIME Cryptographic Signature URL: From calie at uwaterloo.ca Fri Dec 19 22:51:29 2008 From: calie at uwaterloo.ca (Colin Alie) Date: Sat, 20 Dec 2008 09:51:29 +1100 Subject: [Ekiga-list] Ekiga version 2.0.12 no longer compatible with ekiga.net? Message-ID: <200812200951.29609.calie@uwaterloo.ca> Good morning, Palo, as per your suggestion, I configured my router to forward TCP and UDP ports 5060 to my laptop. I then tried calling the echo test (500 at ekiga.net). This time, the call was connected but no audio or video was received from the remote server. So, I'm at the same point I was before I upgraded to version 3.0. Until next time, Colin. From terry1 at beam.ltd.uk Fri Dec 19 22:54:08 2008 From: terry1 at beam.ltd.uk (Terry Barnaby) Date: Fri, 19 Dec 2008 22:54:08 +0000 Subject: [Ekiga-list] No Echo Test response: STUN Problem with Thomson ST585 V6 ADSL router Message-ID: <494C2610.2030800@beam.ltd.uk> 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 ... Cheers Terry From palos at post.sk Fri Dec 19 23:24:17 2008 From: palos at post.sk (Palo S.) Date: 20 Dec 2008 00:24:17 +0100 (CET) Subject: [Ekiga-list] Ekiga version 2.0.12 no longer compatible with ekiga.net? Message-ID: <494C2D21.000001.16230@kamasutra> Hi Colin, I am sorry to hear that it did not help. However, is it possible for you to try the latest snapshot? That should contain a fix for the CANCEL messages accepted by Ekiga that should not be accepted. I did not have the chance to test it yet but it should be there. Palo ----- Origin?lna Spr?va ----- Od: Colin Alie Komu: Poslan?: 19.12.2008 23:51 Predmet: Re: [Ekiga-list] Ekiga version 2.0.12 no longer compatible withekiga.net? > Good morning, > > Palo, as per your suggestion, I configured my router to forward TCP and UDP > ports 5060 to my laptop. I then tried calling the echo test (500 at ekiga.net). > This time, the call was connected but no audio or video was received from the > remote server. So, I\'m at the same point I was before I upgraded to version > 3.0. > > Until next time, Colin. > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > __________ http://zabava.sme.sk/ - Str?nka ?o usmeje ti tv?r From dalbers at gmail.com Sat Dec 20 04:12:04 2008 From: dalbers at gmail.com (Darren Albers) Date: Fri, 19 Dec 2008 23:12:04 -0500 Subject: [Ekiga-list] Thank you Message-ID: <7cd7fc040812192012s5cf6f651ga41ebf4b51b982d5@mail.gmail.com> 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! From leamas.alec at gmail.com Sat Dec 20 13:51:04 2008 From: leamas.alec at gmail.com (Alec Leamas) Date: Sat, 20 Dec 2008 14:51:04 +0100 Subject: [Ekiga-list] Newbie configuration experiences... Message-ID: <494CF848.1050009@gmail.com> 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 From billcollins1.2007 at gmail.com Sat Dec 20 13:55:35 2008 From: billcollins1.2007 at gmail.com (Bill Collins) Date: Sat, 20 Dec 2008 08:55:35 -0500 Subject: [Ekiga-list] Thank you In-Reply-To: <7cd7fc040812192012s5cf6f651ga41ebf4b51b982d5@mail.gmail.com> References: <7cd7fc040812192012s5cf6f651ga41ebf4b51b982d5@mail.gmail.com> Message-ID: <33efb16e0812200555h7d086cd4kdc2284ed60b23d84@mail.gmail.com> 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 at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: From terry1 at beam.ltd.uk Sat Dec 20 14:02:08 2008 From: terry1 at beam.ltd.uk (Terry Barnaby) Date: Sat, 20 Dec 2008 14:02:08 +0000 Subject: [Ekiga-list] Newbie configuration experiences... In-Reply-To: <494CF848.1050009@gmail.com> References: <494CF848.1050009@gmail.com> Message-ID: <494CFAE0.5040706@beam.ltd.uk> 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 at 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 From leamas.alec at gmail.com Sat Dec 20 14:51:26 2008 From: leamas.alec at gmail.com (Alec Leamas) Date: Sat, 20 Dec 2008 15:51:26 +0100 Subject: [Ekiga-list] Newbie configuration experiences... In-Reply-To: <494CFAE0.5040706@beam.ltd.uk> References: <494CF848.1050009@gmail.com> <494CFAE0.5040706@beam.ltd.uk> Message-ID: <494D066E.9040702@gmail.com> 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 at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list From dsandras at seconix.com Sat Dec 20 14:51:57 2008 From: dsandras at seconix.com (Damien Sandras) Date: Sat, 20 Dec 2008 15:51:57 +0100 Subject: [Ekiga-list] could not register : behind a router In-Reply-To: References: <380681.85679.qm@web38303.mail.mud.yahoo.com> <1229373582.13601.45.camel@scorpion.multitel.be> <1229414703.13601.53.camel@scorpion.multitel.be> <4949063A.6070809@gmail.com> <1229542762.4276.8.camel@scorpion.multitel.be> Message-ID: <1229784717.27064.2.camel@scorpion.multitel.be> 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:dsandras at ekiga.net From dsandras at seconix.com Sat Dec 20 14:52:25 2008 From: dsandras at seconix.com (Damien Sandras) Date: Sat, 20 Dec 2008 15:52:25 +0100 Subject: [Ekiga-list] Need info regarding Ekiga Teleconferencing In-Reply-To: <7161431b0812180723o2d18075br32f99b369c4fc42d@mail.gmail.com> References: <7161431b0812180723o2d18075br32f99b369c4fc42d@mail.gmail.com> Message-ID: <1229784745.27064.4.camel@scorpion.multitel.be> 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:dsandras at ekiga.net From dsandras at seconix.com Sat Dec 20 14:54:13 2008 From: dsandras at seconix.com (Damien Sandras) Date: Sat, 20 Dec 2008 15:54:13 +0100 Subject: [Ekiga-list] No Echo Test response: STUN Problem with Thomson ST585 V6 ADSL router In-Reply-To: <494C2610.2030800@beam.ltd.uk> References: <494C2610.2030800@beam.ltd.uk> Message-ID: <1229784853.27064.6.camel@scorpion.multitel.be> Le vendredi 19 d?cembre 2008 ? 22:54 +0000, 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:dsandras at ekiga.net From dsandras at seconix.com Sat Dec 20 14:54:54 2008 From: dsandras at seconix.com (Damien Sandras) Date: Sat, 20 Dec 2008 15:54:54 +0100 Subject: [Ekiga-list] Thank you In-Reply-To: <7cd7fc040812192012s5cf6f651ga41ebf4b51b982d5@mail.gmail.com> References: <7cd7fc040812192012s5cf6f651ga41ebf4b51b982d5@mail.gmail.com> Message-ID: <1229784894.27064.8.camel@scorpion.multitel.be> 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:dsandras at ekiga.net From dsandras at seconix.com Sat Dec 20 15:00:42 2008 From: dsandras at seconix.com (Damien Sandras) Date: Sat, 20 Dec 2008 16:00:42 +0100 Subject: [Ekiga-list] Newbie configuration experiences... In-Reply-To: <494D066E.9040702@gmail.com> References: <494CF848.1050009@gmail.com> <494CFAE0.5040706@beam.ltd.uk> <494D066E.9040702@gmail.com> Message-ID: <1229785242.27064.13.camel@scorpion.multitel.be> 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:dsandras at ekiga.net From dsandras at seconix.com Sat Dec 20 15:01:58 2008 From: dsandras at seconix.com (Damien Sandras) Date: Sat, 20 Dec 2008 16:01:58 +0100 Subject: [Ekiga-list] LDAP Support in Ekiga Windows Version 3.0.0 In-Reply-To: <30A7EEA43B6F2F4285A916732F994B69B04CAD@ex2-del1.synapse.com> References: <30A7EEA43B6F2F4285A916732F994B69B04CAD@ex2-del1.synapse.com> Message-ID: <1229785318.27064.15.camel@scorpion.multitel.be> 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:dsandras at ekiga.net From dsandras at seconix.com Sat Dec 20 15:16:52 2008 From: dsandras at seconix.com (Damien Sandras) Date: Sat, 20 Dec 2008 16:16:52 +0100 Subject: [Ekiga-list] output of "ekiga -d 4 > output.txt 2>&1" for failed call attempt In-Reply-To: <494AA996.8020805@bwh.harvard.edu> References: <494AA996.8020805@bwh.harvard.edu> Message-ID: <1229786212.27064.18.camel@scorpion.multitel.be> 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:dsandras at ekiga.net From leamas.alec at gmail.com Sat Dec 20 15:25:22 2008 From: leamas.alec at gmail.com (Alec Leamas) Date: Sat, 20 Dec 2008 16:25:22 +0100 Subject: [Ekiga-list] No Echo Test response: STUN Problem with Thomson ST585 V6 ADSL router In-Reply-To: <1229784853.27064.6.camel@scorpion.multitel.be> References: <494C2610.2030800@beam.ltd.uk> <1229784853.27064.6.camel@scorpion.multitel.be> Message-ID: <494D0E62.9000303@gmail.com> Damien Sandras wrote: > Le vendredi 19 d?cembre 2008 ? 22:54 +0000, 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 From andre at bwh.harvard.edu Sat Dec 20 15:28:59 2008 From: andre at bwh.harvard.edu (Andre Robatino) Date: Sat, 20 Dec 2008 10:28:59 -0500 Subject: [Ekiga-list] output of "ekiga -d 4 > output.txt 2>&1" for failed call attempt In-Reply-To: <1229786212.27064.18.camel@scorpion.multitel.be> References: <494AA996.8020805@bwh.harvard.edu> <1229786212.27064.18.camel@scorpion.multitel.be> Message-ID: <494D0F3B.70207@bwh.harvard.edu> 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. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3266 bytes Desc: S/MIME Cryptographic Signature URL: From dsandras at seconix.com Sat Dec 20 16:20:29 2008 From: dsandras at seconix.com (Damien Sandras) Date: Sat, 20 Dec 2008 17:20:29 +0100 Subject: [Ekiga-list] Ekiga cannot register with ekiga.net - Asterisk can In-Reply-To: <2e19719f0812141121o6f1a6617jec63b70a333f854a@mail.gmail.com> References: <2e19719f0812141121o6f1a6617jec63b70a333f854a@mail.gmail.com> Message-ID: <1229790029.27064.23.camel@scorpion.multitel.be> 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: > > bent at yosie ~ $ tshark -r ekiga-asterisk.trace > Running as user "bent" and group "users". > 1 0.000000 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) > bent at yosie ~ $ > > whereas Ekiga the softphone doesn't: > > bent at yosie ~ $ tshark -r ekiga.trace > Running as user "bent" and group "users". > 1 0.000000 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:bentb at 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 > bent at 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:dsandras at ekiga.net From dsandras at seconix.com Sat Dec 20 16:21:33 2008 From: dsandras at seconix.com (Damien Sandras) Date: Sat, 20 Dec 2008 17:21:33 +0100 Subject: [Ekiga-list] No Echo Test response: STUN Problem with Thomson ST585 V6 ADSL router In-Reply-To: <494D0E62.9000303@gmail.com> References: <494C2610.2030800@beam.ltd.uk> <1229784853.27064.6.camel@scorpion.multitel.be> <494D0E62.9000303@gmail.com> Message-ID: <1229790093.27064.25.camel@scorpion.multitel.be> Le samedi 20 d?cembre 2008 ? 16:25 +0100, Alec Leamas a ?crit : > Damien Sandras wrote: > > Le vendredi 19 d?cembre 2008 ? 22:54 +0000, 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:dsandras at ekiga.net From terry1 at beam.ltd.uk Sat Dec 20 17:28:26 2008 From: terry1 at beam.ltd.uk (Terry Barnaby) Date: Sat, 20 Dec 2008 17:28:26 +0000 Subject: [Ekiga-list] No Echo Test response: STUN Problem with Thomson ST585 V6 ADSL router In-Reply-To: <1229790093.27064.25.camel@scorpion.multitel.be> References: <494C2610.2030800@beam.ltd.uk> <1229784853.27064.6.camel@scorpion.multitel.be> <494D0E62.9000303@gmail.com> <1229790093.27064.25.camel@scorpion.multitel.be> Message-ID: <494D2B3A.7040203@beam.ltd.uk> 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 +0000, 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 From leamas.alec at gmail.com Sat Dec 20 18:24:24 2008 From: leamas.alec at gmail.com (Alec Leamas) Date: Sat, 20 Dec 2008 19:24:24 +0100 Subject: [Ekiga-list] No Echo Test response: STUN Problem with Thomson ST585 V6 ADSL router In-Reply-To: <1229790093.27064.25.camel@scorpion.multitel.be> References: <494C2610.2030800@beam.ltd.uk> <1229784853.27064.6.camel@scorpion.multitel.be> <494D0E62.9000303@gmail.com> <1229790093.27064.25.camel@scorpion.multitel.be> Message-ID: <494D3858.2090909@gmail.com> 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 From dsandras at seconix.com Sat Dec 20 18:48:52 2008 From: dsandras at seconix.com (Damien Sandras) Date: Sat, 20 Dec 2008 19:48:52 +0100 Subject: [Ekiga-list] output of "ekiga -d 4 > output.txt 2>&1" for failed call attempt In-Reply-To: <494D0F3B.70207@bwh.harvard.edu> References: <494AA996.8020805@bwh.harvard.edu> <1229786212.27064.18.camel@scorpion.multitel.be> <494D0F3B.70207@bwh.harvard.edu> Message-ID: <1229798932.27064.31.camel@scorpion.multitel.be> 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:dsandras at ekiga.net From dsandras at seconix.com Sat Dec 20 18:49:09 2008 From: dsandras at seconix.com (Damien Sandras) Date: Sat, 20 Dec 2008 19:49:09 +0100 Subject: [Ekiga-list] No Echo Test response: STUN Problem with Thomson ST585 V6 ADSL router In-Reply-To: <494D3858.2090909@gmail.com> References: <494C2610.2030800@beam.ltd.uk> <1229784853.27064.6.camel@scorpion.multitel.be> <494D0E62.9000303@gmail.com> <1229790093.27064.25.camel@scorpion.multitel.be> <494D3858.2090909@gmail.com> Message-ID: <1229798949.27064.33.camel@scorpion.multitel.be> 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:dsandras at ekiga.net From andre at bwh.harvard.edu Sat Dec 20 19:07:22 2008 From: andre at bwh.harvard.edu (Andre Robatino) Date: Sat, 20 Dec 2008 14:07:22 -0500 Subject: [Ekiga-list] output of "ekiga -d 4 > output.txt 2>&1" for failed call attempt In-Reply-To: <1229798932.27064.31.camel@scorpion.multitel.be> References: <494AA996.8020805@bwh.harvard.edu> <1229786212.27064.18.camel@scorpion.multitel.be> <494D0F3B.70207@bwh.harvard.edu> <1229798932.27064.31.camel@scorpion.multitel.be> Message-ID: <494D426A.5000307@bwh.harvard.edu> 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. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3266 bytes Desc: S/MIME Cryptographic Signature URL: From palos at post.sk Sat Dec 20 19:33:13 2008 From: palos at post.sk (Palo S.) Date: 20 Dec 2008 20:33:13 +0100 (CET) Subject: [Ekiga-list] \"remote user cleared the call\" problem Message-ID: <494D4879.000001.10484@kamasutra> > > 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:dsandras at ekiga.net > > > > > > _______________________________________________ > > ekiga-list mailing list > > ekiga-list at 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 at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > __________ http://zabava.sme.sk/ - Str?nka ?o usmeje ti tv?r From dalbers at gmail.com Sat Dec 20 21:38:56 2008 From: dalbers at gmail.com (Darren Albers) Date: Sat, 20 Dec 2008 16:38:56 -0500 Subject: [Ekiga-list] Thank you In-Reply-To: <33efb16e0812200555h7d086cd4kdc2284ed60b23d84@mail.gmail.com> References: <7cd7fc040812192012s5cf6f651ga41ebf4b51b982d5@mail.gmail.com> <33efb16e0812200555h7d086cd4kdc2284ed60b23d84@mail.gmail.com> Message-ID: <7cd7fc040812201338s4b4776f4yf5c99e855f21a187@mail.gmail.com> 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 From peasthope at shaw.ca Sat Dec 20 22:40:20 2008 From: peasthope at shaw.ca (PETER EASTHOPE) Date: Sat, 20 Dec 2008 14:40:20 -0800 Subject: [Ekiga-list] Re (2): failure in registration of sip account Message-ID: 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/ From claudio at dim.uchile.cl Sun Dec 21 06:58:01 2008 From: claudio at dim.uchile.cl (Claudio Baeza Retamal) Date: Sun, 21 Dec 2008 03:58:01 -0300 Subject: [Ekiga-list] Logitech Quickam Pro 9000 and ekiga Message-ID: <1229842681.11489.33.camel@asteriscos-casa.dim.uchile.cl> 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 From edmund.laugasson at eesti.ee Sun Dec 21 07:09:23 2008 From: edmund.laugasson at eesti.ee (Edmund Laugasson) Date: Sun, 21 Dec 2008 09:09:23 +0200 Subject: [Ekiga-list] problem compiling Ekiga 3.0.1 under Kubuntu 8.04.1 LTS Message-ID: <494DEBA3.6080109@eesti.ee> 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 From jpuydt at free.fr Sun Dec 21 08:57:36 2008 From: jpuydt at free.fr (Julien Puydt) Date: Sun, 21 Dec 2008 09:57:36 +0100 Subject: [Ekiga-list] Logitech Quickam Pro 9000 and ekiga In-Reply-To: <1229842681.11489.33.camel@asteriscos-casa.dim.uchile.cl> References: <1229842681.11489.33.camel@asteriscos-casa.dim.uchile.cl> Message-ID: <494E0500.8060008@free.fr> Claudio Baeza Retamal a ?crit : > 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? Install the V4L2 package (the name must look like ptlib-plugin-v4l2 or some such). Snark on #ekiga From dsandras at seconix.com Sun Dec 21 09:25:16 2008 From: dsandras at seconix.com (Damien Sandras) Date: Sun, 21 Dec 2008 10:25:16 +0100 Subject: [Ekiga-list] output of "ekiga -d 4 > output.txt 2>&1" for failed call attempt In-Reply-To: <494D426A.5000307@bwh.harvard.edu> References: <494AA996.8020805@bwh.harvard.edu> <1229786212.27064.18.camel@scorpion.multitel.be> <494D0F3B.70207@bwh.harvard.edu> <1229798932.27064.31.camel@scorpion.multitel.be> <494D426A.5000307@bwh.harvard.edu> Message-ID: <1229851516.4259.0.camel@scorpion.multitel.be> Le samedi 20 d?cembre 2008 ? 14:07 -0500, Andre Robatino a ?crit : > 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. I understand, however, I do not understand why Ekiga 3 would 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:dsandras at ekiga.net From dsandras at seconix.com Sun Dec 21 09:28:40 2008 From: dsandras at seconix.com (Damien Sandras) Date: Sun, 21 Dec 2008 10:28:40 +0100 Subject: [Ekiga-list] Re (2): failure in registration of sip account In-Reply-To: References: Message-ID: <1229851720.4259.4.camel@scorpion.multitel.be> Le samedi 20 d?cembre 2008 ? 14:40 -0800, PETER EASTHOPE a ?crit : > 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. > Do you have something like this: deb http://ftp.fr.debian.org/debian experimental main contrib non-free in /etc/apt/sources.list -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From dsandras at seconix.com Sun Dec 21 09:31:50 2008 From: dsandras at seconix.com (Damien Sandras) Date: Sun, 21 Dec 2008 10:31:50 +0100 Subject: [Ekiga-list] \"remote user cleared the call\" problem In-Reply-To: <494D4879.000001.10484@kamasutra> References: <494D4879.000001.10484@kamasutra> Message-ID: <1229851910.4259.8.camel@scorpion.multitel.be> Le samedi 20 d?cembre 2008 ? 20:33 +0100, Palo S. a ?crit : > > > 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. > You need the latest TRUNK for opal, ptlib and ekiga. Please note that lastest TRUNK is broken with video. If you want something stable, I would suggest to follow this: http://wiki.ekiga.org/index.php/SVN (and use the gnome-2-24 instructions) -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From dsandras at seconix.com Sun Dec 21 09:32:52 2008 From: dsandras at seconix.com (Damien Sandras) Date: Sun, 21 Dec 2008 10:32:52 +0100 Subject: [Ekiga-list] problem compiling Ekiga 3.0.1 under Kubuntu 8.04.1 LTS In-Reply-To: <494DEBA3.6080109@eesti.ee> References: <494DEBA3.6080109@eesti.ee> Message-ID: <1229851972.4259.10.camel@scorpion.multitel.be> Le dimanche 21 d?cembre 2008 ? 09:09 +0200, Edmund Laugasson a ?crit : > 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. > Do you have xml2po on your system ? -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From leamas.alec at gmail.com Sun Dec 21 14:43:01 2008 From: leamas.alec at gmail.com (Alec Leamas) Date: Sun, 21 Dec 2008 15:43:01 +0100 Subject: [Ekiga-list] No Echo Test response: STUN Problem with Thomson ST585 V6 ADSL router In-Reply-To: <494D2B3A.7040203@beam.ltd.uk> References: <494C2610.2030800@beam.ltd.uk> <1229784853.27064.6.camel@scorpion.multitel.be> <494D0E62.9000303@gmail.com> <1229790093.27064.25.camel@scorpion.multitel.be> <494D2B3A.7040203@beam.ltd.uk> Message-ID: <494E55F5.1010001@gmail.com> Checking my logs... is it so that I hijacked Terry's thread and thus, after submitting a bug seemingly closing the thread, caused his question to remain unsolved? If so, I really have to apologize. --alec Terry Barnaby wrote: [snip] >> 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 at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list From Eugen.Dedu at pu-pm.univ-fcomte.fr Sun Dec 21 19:00:20 2008 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Sun, 21 Dec 2008 20:00:20 +0100 Subject: [Ekiga-list] Debian packages Message-ID: <494E9244.4030701@pu-pm.univ-fcomte.fr> Hi, I think that currently trunk is much more important than stable branch (which is rarely modified), so, starting from now, ekiga-snapshot will use the trunk version, not the stable branch. Please let me know if it is really a problem for you. More information below: ============ This email summarises information about debian packages on ekiga Web site, http://snapshots.ekiga.net. This site provides three kinds of packages: 1. one package for non-free codecs, to be installed together with official debian packages currently from experimental (stable release) 2. snapshot packages from the stable branch (which should be more stable than official debian's ones) <-- this is not provided anymore, you can use debian's official ones 3. snapshot packages from the trunk (unstable), this is package ekiga-snapshot More information can be found at http://snapshots.ekiga.net (will be updated shortly). Cheers, -- Eugen Dedu From Eugen.Dedu at pu-pm.univ-fcomte.fr Sun Dec 21 19:32:16 2008 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Sun, 21 Dec 2008 20:32:16 +0100 Subject: [Ekiga-list] Re (2): failure in registration of sip account In-Reply-To: <1229851720.4259.4.camel@scorpion.multitel.be> References: <1229851720.4259.4.camel@scorpion.multitel.be> Message-ID: <494E99C0.9030807@pu-pm.univ-fcomte.fr> Damien Sandras wrote: > Le samedi 20 d?cembre 2008 ? 14:40 -0800, PETER EASTHOPE a ?crit : >> 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 You should replace deb-src by deb. -- Eugen From ml at stdout.at Sun Dec 21 19:55:19 2008 From: ml at stdout.at (Hannes Ebner) Date: Sun, 21 Dec 2008 20:55:19 +0100 Subject: [Ekiga-list] Debian packages In-Reply-To: <494E9244.4030701@pu-pm.univ-fcomte.fr> References: <494E9244.4030701@pu-pm.univ-fcomte.fr> Message-ID: <494E9F27.2020600@stdout.at> Hi Eugen, Eugen Dedu wrote: > 3. snapshot packages from the trunk (unstable), this is package > ekiga-snapshot I saw that there are packages for Ubuntu Hardy and Gutsy, but not for Intrepid - the same applies to the stable packages. Do you have any plans for providing packages for Ubuntu 8.10? Thanks, Hannes From rick at niof.net Sun Dec 21 20:33:42 2008 From: rick at niof.net (Rick Pasotto) Date: Sun, 21 Dec 2008 15:33:42 -0500 Subject: [Ekiga-list] Debian packages In-Reply-To: <494E9244.4030701@pu-pm.univ-fcomte.fr> References: <494E9244.4030701@pu-pm.univ-fcomte.fr> Message-ID: <20081221203342.GT5641@niof.net> gnome-desktop-environment depends on ekiga (>= 2.0.12) Since 'aptitude install ekiga-snapshot' removes ekiga, gnome-desktop-environment becomes BROKEN and the installation would REMOVE 47 other packages. As far as I'm concerned, this means that ekiga-snapshot is NOT installable. I think that the problem is that the version number for ekiga-snapshot is 0-20081220-1 which is less than 2.0.12. Perhaps if the version number were changed to something greater that 2.0.12 (eg, 3-20081220-1) then the problem would go away. -- "Fall seven times. Stand up eight." -- Japanese Proverb Rick Pasotto rick at niof.net http://www.niof.net From Eugen.Dedu at pu-pm.univ-fcomte.fr Sun Dec 21 21:46:27 2008 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Sun, 21 Dec 2008 22:46:27 +0100 Subject: [Ekiga-list] Debian packages In-Reply-To: <20081221203342.GT5641@niof.net> References: <494E9244.4030701@pu-pm.univ-fcomte.fr> <20081221203342.GT5641@niof.net> Message-ID: <494EB933.2040408@pu-pm.univ-fcomte.fr> Rick Pasotto wrote: > gnome-desktop-environment depends on ekiga (>= 2.0.12) > > Since 'aptitude install ekiga-snapshot' removes ekiga, > gnome-desktop-environment becomes BROKEN and the installation > would REMOVE 47 other packages. > > As far as I'm concerned, this means that ekiga-snapshot is NOT > installable. > > I think that the problem is that the version number for ekiga-snapshot > is 0-20081220-1 which is less than 2.0.12. Perhaps if the version number > were changed to something greater that 2.0.12 (eg, 3-20081220-1) then > the problem would go away. It seems you're right. I change that for tomorrow probably. Thanks! -- Eugen From peasthope at shaw.ca Mon Dec 22 00:59:46 2008 From: peasthope at shaw.ca (peasthope at shaw.ca) Date: Sun, 21 Dec 2008 16:59:46 -0800 Subject: [Ekiga-list] Usage of Ekiga 3. Was "failure in registration of sip account". Message-ID: Folk, Eugen Dedu wrote, ed> "You should replace deb-src by deb." Done; thanks. Damien Sandras wrote, ds> "Rebooted ?" Just in case some /tmp/* files would cause confusion. ds> "... apt-get update ?" Oops! Thanks. Normally I use dselect. OK; now Ekiga 3.0.1 is present and working, ... and there are many new questions. (1) Ekiga 2 used two accounts: "ekiga.net SIP Service" and "Ekiga PC-To-Phone". Now "Ekiga Call Out" is also present and appears to duplicate PC-To-Phone. Can one of these be removed without harm? (2) The Contacts within Ekiga and the Address Book have similar functions. Is the Address Book being phased out? (3) The sip addresses and phone numbers are gone from the Address Book. Only the names remain. Can the addresses and numbers be recovered? Enough for now. Thanks for all the work and discussion, ... Peter E. -- http://members.shaw.ca/peasthope/ http://carnot.yi.org/ = http://carnot.pathology.ubc.ca/ From dsandras at seconix.com Mon Dec 22 08:43:32 2008 From: dsandras at seconix.com (Damien Sandras) Date: Mon, 22 Dec 2008 09:43:32 +0100 Subject: [Ekiga-list] Usage of Ekiga 3. Was "failure in registration of sip account". In-Reply-To: References: Message-ID: <1229935412.4472.3.camel@scorpion.multitel.be> Le dimanche 21 d?cembre 2008 ? 16:59 -0800, peasthope at shaw.ca a ?crit : > Folk, > > Eugen Dedu wrote, > ed> "You should replace deb-src by deb." > > Done; thanks. > > Damien Sandras wrote, > ds> "Rebooted ?" > Just in case some /tmp/* files would cause confusion. > > ds> "... apt-get update ?" > > Oops! Thanks. Normally I use dselect. > > OK; now Ekiga 3.0.1 is present and working, > ... and there are many new questions. > > (1) Ekiga 2 used two accounts: "ekiga.net > SIP Service" and "Ekiga PC-To-Phone". > Now "Ekiga Call Out" is also present and appears > to duplicate PC-To-Phone. Can one of these be > removed without harm? Yes (the old one). > (2) The Contacts within Ekiga and the Address Book > have similar functions. Is the Address Book being > phased out? No, it is seen as a source of Contacts. The "Roster" is just your contacts list. You can add contacts from the addressbook into the roster. > (3) The sip addresses and phone numbers are gone > from the Address Book. Only the names remain. > Can the addresses and numbers be recovered? If you right click, they should be available. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From michel.memeteau at gmail.com Mon Dec 22 22:22:41 2008 From: michel.memeteau at gmail.com (michel memeteau) Date: Mon, 22 Dec 2008 23:22:41 +0100 Subject: [Ekiga-list] Status of Echo test ? Message-ID: Hi All , With the great work from the Ekiga team the Echo test in H264 is really great , I tested it on Ekiga3 Windows , and it really makes a difference when you want to show the quality ( even stuff like skype don't have this option ) However , I frequently have to set up some mac or Windows machine and finish with Xlite or some other limited software in order to keep on using SIP ( and not let people fall on the tentation of using skype ...) , and in order to test their setup , I was looking for an echo test who support either H263 or H263-98 as Xlite does not support either H261 nor H264 for some ridiculous reasons .... Do you know any ? or how is this difficult to make ekiga * works with those two codecs ? thanks -- %<------------------------------------------------------->% Michel memeteau Blog 0.2 : http://memeteau.free.fr Fixe : 0974763294 Mobile : 0624808051 VOIP | Visio: sip:freechelmi at ippi.fr jabber/GTalk : xmpp:freechelmi at jabber.fr -------------- next part -------------- An HTML attachment was scrubbed... URL: From jeroen.vangoey at gmail.com Mon Dec 22 22:59:50 2008 From: jeroen.vangoey at gmail.com (Jeroen Van Goey) Date: Mon, 22 Dec 2008 23:59:50 +0100 Subject: [Ekiga-list] ekiga gives segmentation fault and will not start up Message-ID: Hey, When I click on the ekiga icon in Ubuntu 8.10, it gives a a spinning wheel and then stops. It never even opens. When I start ekiga via the command line with debugging on, I get the following error. Code: ~$ ekiga -d 4 2008/12/16 21:37:44.747 0:00.213 ekiga ekiga Version 2.0.12 by on Unix Linux (2.6.27-9-generic-x86_64) at 2008/12/16 21:37:44.746 2008/12/16 21:37:45.049 0:00.515 ekiga Detected audio plugins: ALSA 2008/12/16 21:37:45.050 0:00.516 ekiga Detected video plugins: Picture,V4L2,V4L 2008/12/16 21:37:45.051 0:00.517 ekiga Detected audio plugins: ALSA 2008/12/16 21:37:45.052 0:00.518 ekiga Detected video plugins: Picture,V4L2,V4L 2008/12/16 21:37:45.053 0:00.519 ekiga Detecting V4L2 devices 2008/12/16 21:37:45.054 0:00.520 ekiga Unable to detect v4l2 directory 2008/12/16 21:37:45.188 0:00.654 ekiga Detected the following audio input devices: Default,HDA Intel with plugin ALSA 2008/12/16 21:37:45.189 0:00.655 ekiga Detected the following audio output devices: Default,HDA Intel with plugin ALSA 2008/12/16 21:37:45.190 0:00.656 ekiga Detected the following video input devices: No device found with plugin V4L2 2008/12/16 21:37:45.191 0:00.657 ekiga Detected the following audio input devices: Default,HDA Intel with plugin ALSA 2008/12/16 21:37:45.192 0:00.658 ekiga Detected the following audio output devices: Default,HDA Intel with plugin ALSA 2008/12/16 21:37:45.193 0:00.660 ekiga Detected the following video input devices: No device found with plugin V4L2 Entity: line 2: parser error : invalid character in attribute value From peasthope at shaw.ca Tue Dec 23 01:42:04 2008 From: peasthope at shaw.ca (peasthope at shaw.ca) Date: Mon, 22 Dec 2008 17:42:04 -0800 Subject: [Ekiga-list] Re^3: Usage of Ekiga 3. Was "failure in registration of sip account". Message-ID: Damien & others, As you suggested, account registration is more reliable in this release; no failures in three startups. Good! At Monday, December 22, 2008 0:43 Damien Sandras wrote, ds> You can add contacts from the addressbook into the roster. pe > (3) The sip addresses and phone numbers are gone pe > from the Address Book. Only the names remain. pe > Can the addresses and numbers be recovered? ds> If you right click, they should be available. Only the first entry has addresses. The other entries are names only. I tried to insert the first entry into the contact roster. All the Ekiga windows became frozen. This photo is poor but gives the impression. http://carnot.yi.org/EkigaScreen.jpg The foremost window is entitled "Add to local roster". The Ekiga process was killed to recover a healthy GUI. The echo test to sip:500 at ekiga.net works. Otherwise none of the few attempted calls succeeded. Perhaps some of these problems occur from using Xfce4 rather than Gnome. Thanks the extensive work, ... Peter E. -- http://members.shaw.ca/peasthope/ http://carnot.yi.org/ = http://carnot.pathology.ubc.ca/ From sevmek at free.fr Tue Dec 23 13:14:07 2008 From: sevmek at free.fr (yannick) Date: Tue, 23 Dec 2008 14:14:07 +0100 Subject: [Ekiga-list] xmas theme for ekiga.net Message-ID: <1230038047.10105.72.camel@achille> Hi, For those who live in countries celebrating xmas, I made a special short-time lived theme for ekiga.net https://www.ekiga.net/ Best regards, Yannick From dsandras at seconix.com Tue Dec 23 18:22:35 2008 From: dsandras at seconix.com (Damien Sandras) Date: Tue, 23 Dec 2008 19:22:35 +0100 Subject: [Ekiga-list] Status of Echo test ? In-Reply-To: References: Message-ID: <1230056555.4710.44.camel@scorpion.multitel.be> Hi, Le lundi 22 d?cembre 2008 ? 23:22 +0100, michel memeteau a ?crit : > Hi All , With the great work from the Ekiga team the Echo test in H264 > is really great , I tested it on Ekiga3 Windows , and it really makes > a difference when you want to show the quality ( even stuff like skype > don't have this option ) > > However , I frequently have to set up some mac or Windows machine and > finish with Xlite or some other limited software in order to keep on > using SIP ( and not let people fall on the tentation of using > skype ...) , and in order to test their setup , I was looking for an > echo test who support either H263 or H263-98 as Xlite does not support > either H261 nor H264 for some ridiculous reasons .... > > Do you know any ? or how is this difficult to make ekiga * works with > those two codecs ? thanks > I just activated h263 and h263p on ekiga.net. Can you try to see if it works or not ? -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From dsandras at seconix.com Tue Dec 23 18:23:38 2008 From: dsandras at seconix.com (Damien Sandras) Date: Tue, 23 Dec 2008 19:23:38 +0100 Subject: [Ekiga-list] ekiga gives segmentation fault and will not start up In-Reply-To: References: Message-ID: <1230056618.4710.46.camel@scorpion.multitel.be> Hi, Le lundi 22 d?cembre 2008 ? 23:59 +0100, Jeroen Van Goey a ?crit : > Hey, > > When I click on the ekiga icon in Ubuntu 8.10, it gives a a spinning > wheel and then stops. It never even opens. > > When I start ekiga via the command line with debugging on, I get the > following error. > > Code: > > base_uri="file:///home/tr/.evolution/addr I think it is an evolution-data-server error. Does evolution work ? -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From Eugen.Dedu at pu-pm.univ-fcomte.fr Tue Dec 23 18:24:44 2008 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Tue, 23 Dec 2008 19:24:44 +0100 Subject: [Ekiga-list] Debian packages In-Reply-To: <494E9F27.2020600@stdout.at> References: <494E9244.4030701@pu-pm.univ-fcomte.fr> <494E9F27.2020600@stdout.at> Message-ID: <49512CEC.2090107@pu-pm.univ-fcomte.fr> Hannes Ebner wrote: > Hi Eugen, > > Eugen Dedu wrote: >> 3. snapshot packages from the trunk (unstable), this is package >> ekiga-snapshot > > I saw that there are packages for Ubuntu Hardy and Gutsy, but not for > Intrepid - the same applies to the stable packages. Do you have any > plans for providing packages for Ubuntu 8.10? Hi Hannes, Please wait, they should be available in a few days... -- Eugen From dsandras at seconix.com Tue Dec 23 18:25:51 2008 From: dsandras at seconix.com (Damien Sandras) Date: Tue, 23 Dec 2008 19:25:51 +0100 Subject: [Ekiga-list] Re^3: Usage of Ekiga 3. Was "failure in registration of sip account". In-Reply-To: References: Message-ID: <1230056751.4710.50.camel@scorpion.multitel.be> Le lundi 22 d?cembre 2008 ? 17:42 -0800, peasthope at shaw.ca a ?crit : > Damien & others, > > As you suggested, account registration is more reliable > in this release; no failures in three startups. Good! Good! > At Monday, December 22, 2008 0:43 Damien Sandras wrote, > ds> You can add contacts from the addressbook into the roster. > > pe > (3) The sip addresses and phone numbers are gone > pe > from the Address Book. Only the names remain. > pe > Can the addresses and numbers be recovered? > > ds> If you right click, they should be available. > > Only the first entry has addresses. The other entries > are names only. Just add adresses: you can edit contacts. > I tried to insert the first entry into the contact > roster. All the Ekiga windows became frozen. > This photo is poor but gives the impression. > http://carnot.yi.org/EkigaScreen.jpg > The foremost window is entitled "Add to local roster". > The Ekiga process was killed to recover a healthy GUI. It is probably a bug unfortunately. > The echo test to sip:500 at ekiga.net works. > Otherwise none of the few attempted calls succeeded. Perhaps you should provide a -d4 output. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From sevmek at free.fr Tue Dec 23 21:02:40 2008 From: sevmek at free.fr (yannick) Date: Tue, 23 Dec 2008 22:02:40 +0100 Subject: [Ekiga-list] Status of Echo test ? In-Reply-To: <1230056555.4710.44.camel@scorpion.multitel.be> References: <1230056555.4710.44.camel@scorpion.multitel.be> Message-ID: <1230066160.10105.82.camel@achille> Le mardi 23 d?cembre 2008 ? 19:22 +0100, Damien Sandras a ?crit : > Hi, > > Le lundi 22 d?cembre 2008 ? 23:22 +0100, michel memeteau a ?crit : > > Hi All , With the great work from the Ekiga team the Echo test in H264 > > is really great , I tested it on Ekiga3 Windows , and it really makes > > a difference when you want to show the quality ( even stuff like skype > > don't have this option ) > > > > However , I frequently have to set up some mac or Windows machine and > > finish with Xlite or some other limited software in order to keep on > > using SIP ( and not let people fall on the tentation of using > > skype ...) , and in order to test their setup , I was looking for an > > echo test who support either H263 or H263-98 as Xlite does not support > > either H261 nor H264 for some ridiculous reasons .... > > > > Do you know any ? or how is this difficult to make ekiga * works with > > those two codecs ? thanks > > > > I just activated h263 and h263p on ekiga.net. Can you try to see if it > works or not ? h263p works here. Can you add theora too? this one is free and will be available everywhere... > -- > _ Damien Sandras > (o- > //\ Ekiga Softphone : http://www.ekiga.org/ > v_/_ Be IP : http://www.beip.be/ > FOSDEM : http://www.fosdem.org/ > SIP Phone : sip:dsandras at ekiga.net > > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list -- Me joindre en t?l?phonie IP / vid?oconf?rence ? sip:yannick at ekiga.net Logiciel de VoIP Ekiga : http://www.ekiga.org http://wiki.ekiga.org/index.php/Which_programs_work_with_Ekiga_%3F From dsandras at seconix.com Tue Dec 23 21:06:06 2008 From: dsandras at seconix.com (Damien Sandras) Date: Tue, 23 Dec 2008 22:06:06 +0100 Subject: [Ekiga-list] Status of Echo test ? In-Reply-To: <1230066160.10105.82.camel@achille> References: <1230056555.4710.44.camel@scorpion.multitel.be> <1230066160.10105.82.camel@achille> Message-ID: <1230066366.4710.52.camel@scorpion.multitel.be> Le mardi 23 d?cembre 2008 ? 22:02 +0100, yannick a ?crit : > Le mardi 23 d?cembre 2008 ? 19:22 +0100, Damien Sandras a ?crit : > > Hi, > > > > Le lundi 22 d?cembre 2008 ? 23:22 +0100, michel memeteau a ?crit : > > > Hi All , With the great work from the Ekiga team the Echo test in H264 > > > is really great , I tested it on Ekiga3 Windows , and it really makes > > > a difference when you want to show the quality ( even stuff like skype > > > don't have this option ) > > > > > > However , I frequently have to set up some mac or Windows machine and > > > finish with Xlite or some other limited software in order to keep on > > > using SIP ( and not let people fall on the tentation of using > > > skype ...) , and in order to test their setup , I was looking for an > > > echo test who support either H263 or H263-98 as Xlite does not support > > > either H261 nor H264 for some ridiculous reasons .... > > > > > > Do you know any ? or how is this difficult to make ekiga * works with > > > those two codecs ? thanks > > > > > > > I just activated h263 and h263p on ekiga.net. Can you try to see if it > > works or not ? > > h263p works here. > > Can you add theora too? this one is free and will be available > everywhere... I don't think Asterisk works with theora. At least not without a recompilation on ekiga.net. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From ml at stdout.at Tue Dec 23 21:41:11 2008 From: ml at stdout.at (Hannes Ebner) Date: Tue, 23 Dec 2008 22:41:11 +0100 Subject: [Ekiga-list] Debian packages In-Reply-To: <49512CEC.2090107@pu-pm.univ-fcomte.fr> References: <494E9244.4030701@pu-pm.univ-fcomte.fr> <494E9F27.2020600@stdout.at> <49512CEC.2090107@pu-pm.univ-fcomte.fr> Message-ID: <49515AF7.60008@stdout.at> Eugen Dedu wrote: > Please wait, they should be available in a few days... Great, thanks! /Hannes From torsten.crass at eBiology.de Tue Dec 23 22:26:33 2008 From: torsten.crass at eBiology.de (Torsten Crass) Date: Tue, 23 Dec 2008 23:26:33 +0100 Subject: [Ekiga-list] Trouble getting cross-plattform video to work Message-ID: <49516599.5040807@eBiology.de> Dear List, for about two days I've been trying to get a video chat connection between a Linux (Debian Sid with Ekiga from Experimental) box and a laptop running Windows XP (Ekiga 3.0.2beta) to work. *Very* occasionally I did get bi-directional video, but I wasn't able to determine any hard criteria when it would work and when it wouldn't. Anybody out there having successfully video-chatted between Lin and Win? And if so, may I ask which settings you've been using? Audio/Video codecs, webcam resolution, video bitrate, quality/framerate settings, type of internet connection...? Thanks for any hints -- Torsten From sevmek at free.fr Tue Dec 23 22:36:02 2008 From: sevmek at free.fr (yannick) Date: Tue, 23 Dec 2008 23:36:02 +0100 Subject: [Ekiga-list] Trouble getting cross-plattform video to work In-Reply-To: <49516599.5040807@eBiology.de> References: <49516599.5040807@eBiology.de> Message-ID: <1230071762.10105.90.camel@achille> Le mardi 23 d?cembre 2008 ? 23:26 +0100, Torsten Crass a ?crit : > Dear List, > > for about two days I've been trying to get a video chat connection > between a Linux (Debian Sid with Ekiga from Experimental) box and a > laptop running Windows XP (Ekiga 3.0.2beta) to work. *Very* occasionally > I did get bi-directional video, but I wasn't able to determine any hard > criteria when it would work and when it wouldn't. > > Anybody out there having successfully video-chatted between Lin and Win? > And if so, may I ask which settings you've been using? Audio/Video > codecs, webcam resolution, video bitrate, quality/framerate settings, > type of internet connection...? > > Thanks for any hints -- Hi, >From time to time I chat with a friend using vista. I'm using ekiga 3.0.0 and he is using http://snapshots.ekiga.net/snapshots/win32/archives/ekiga-setup-3.0.2beta-7316.exe On both side we are directly connected to internet using an ADSL line. We usually use speex and theora at 320x200. Some time we have to switch the one calling to get the connection but i'm using quite a quite old 3.0.0 ... Our main issue is some echo with sound, but i still need to verify my sound setup (and ALSA just p... me off!). We usually chat for hours without trouble. Regards, Yannick > > Torsten > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > -- Me joindre en t?l?phonie IP / vid?oconf?rence ? sip:yannick at ekiga.net Logiciel de VoIP Ekiga : http://www.ekiga.org http://wiki.ekiga.org/index.php/Which_programs_work_with_Ekiga_%3F From torsten.crass at eBiology.de Tue Dec 23 23:14:31 2008 From: torsten.crass at eBiology.de (Torsten Crass) Date: Wed, 24 Dec 2008 00:14:31 +0100 Subject: [Ekiga-list] Trouble getting cross-plattform video to work In-Reply-To: <1230071762.10105.90.camel@achille> References: <49516599.5040807@eBiology.de> <1230071762.10105.90.camel@achille> Message-ID: <495170D7.3020401@eBiology.de> Yannick, > Le mardi 23 d?cembre 2008 ? 23:26 +0100, Torsten Crass a ?crit : wow, *that* I call a quick response... :-) >>From time to time I chat with a friend using vista. I'm using ekiga > 3.0.0 and he is using In Debian, it's the 3.0.1 version already. Shouldn't make a big difference, should it? > http://snapshots.ekiga.net/snapshots/win32/archives/ekiga-setup-3.0.2beta-7316.exe The Windows version I've installed is called 3.0.2beta-7316d. > On both side we are directly connected to internet using an ADSL line. We've got ADSL (WAN IP via DynDNS, DHCP on the LAN side), too, and the router says that we have an uplink speed of 400something kBit/s. In my test setup, however, both clients are sitting behind the same router. I don't know exactly which route the streams will take in a sip-initiated video chat, but even if both clients' streams are routed out of the LAN (to where?) and back again, there should be sufficient bandwidth at, say, a per-client video bitrate of 64 kBit/s max, right? (Anyway, I suppose tomorrow I will try to connect to our home network from some other people's place, perhaps that will work better.) Alas, even between two Linux machines it frequently happens that onyl one client recieve's the other's remote video. (It's a pitty Ekiga isn't too talkative about things having gone wrong... Well, it *does* apparently provide some information about the current connection in its status line, but so far I couldn't find any explanation of what "A:8.0/0.0, V:8.3/0.0" actually stands for...) > We usually use speex and theora at 320x200. Ok, sound's familiar. My webcams (two Logitech QuickCam E3500 Plus) offer resolution like 176x144 and 320x240, both of which I tried out. > Some time we have to switch > the one calling to get the connection but i'm using quite a quite old What exactly do you mean by "switch" -- is it like hanging up and re-connecting? For me, this occasionally did help, but by far not always... > 3.0.0 ... Our main issue is some echo with sound, but i still need to > verify my sound setup (and ALSA just p... me off!). Yeah, it's a pitty many aspects of multimedia still kinda suck under Linux... Just ordered an old used Soundblaster boards since neither my current (well, actually not so current anymore...) Yamaha sound card, nor any other current wavetable card seem to be supported. > We usually chat for > hours without trouble. *sigh* Lucky you! Anyway, definitely bed time now. There will be a whole lot of very pleasant, but also somewhat exhausting familiy business to be dealt with tomorrow... Thanks a lot for your reply (further hints still wellcome), best regards and (huh, 00:14 already!) merry Christmas -- Torsten From sevmek at free.fr Tue Dec 23 23:51:23 2008 From: sevmek at free.fr (yannick) Date: Wed, 24 Dec 2008 00:51:23 +0100 Subject: [Ekiga-list] Trouble getting cross-plattform video to work In-Reply-To: <495170D7.3020401@eBiology.de> References: <49516599.5040807@eBiology.de> <1230071762.10105.90.camel@achille> <495170D7.3020401@eBiology.de> Message-ID: <1230076284.10105.96.camel@achille> Le mercredi 24 d?cembre 2008 ? 00:14 +0100, Torsten Crass a ?crit : > both clients are sitting behind the same router That might explain your trouble, the test ekiga use to get your internet IP might confuse the 2 clients as they have the same public IP. The best I can think of is try to setup bonjour for windows http://support.apple.com/downloads/Bonjour_for_Windows Then clients should automatically appears in the roster. Best regards, Yannick From sevmek at free.fr Wed Dec 24 00:02:17 2008 From: sevmek at free.fr (yannick) Date: Wed, 24 Dec 2008 01:02:17 +0100 Subject: [Ekiga-list] Trouble getting cross-plattform video to work In-Reply-To: <1230076284.10105.96.camel@achille> References: <49516599.5040807@eBiology.de> <1230071762.10105.90.camel@achille> <495170D7.3020401@eBiology.de> <1230076284.10105.96.camel@achille> Message-ID: <1230076937.10105.100.camel@achille> Le mercredi 24 d?cembre 2008 ? 00:51 +0100, yannick a ?crit : > Le mercredi 24 d?cembre 2008 ? 00:14 +0100, Torsten Crass a ?crit : > > both clients are sitting behind the same router > > That might explain your trouble, the test ekiga use to get your internet > IP might confuse the 2 clients as they have the same public IP. The best > I can think of is try to setup bonjour for windows > http://support.apple.com/downloads/Bonjour_for_Windows > > Then clients should automatically appears in the roster. > Damien, if i understand correctly the situation STUN gives both client the same IP. When client A try to signaling with client B, ekiga.net gives the IP of client B to client A; is there a test to check if both IP are the the same to pop up an error message ? Maybe with a link to our wiki? Is it worth to report feature request in bugzilla for this? > Best regards, > Yannick -- Me joindre en t?l?phonie IP / vid?oconf?rence ? sip:yannick at ekiga.net Logiciel de VoIP Ekiga : http://www.ekiga.org http://wiki.ekiga.org/index.php/Which_programs_work_with_Ekiga_%3F From palos at post.sk Wed Dec 24 00:25:57 2008 From: palos at post.sk (Palo S.) Date: 24 Dec 2008 01:25:57 +0100 (CET) Subject: [Ekiga-list] \"remote user cleared the call\" problem Message-ID: <49518195.000001.25125@kamasutra> I can confirm that this problem is fixed. The call is not canceled anymore (although I only tested via VNC ie nobody on the other side so I cannot say whether there are some other issues such as voice not coming through). Good job! Palo ----- Origin?lna Spr?va ----- Od: Damien Sandras Komu: Ekiga mailing list Poslan?: 21.12.2008 10:31 Predmet: Re: [Ekiga-list] \\\"remote user cleared the call\\\" problem > Le samedi 20 d??cembre 2008 ?? 20:33 +0100, Palo S. a ??crit : > > > > 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. > > > > You need the latest TRUNK for opal, ptlib and ekiga. Please note that > lastest TRUNK is broken with video. > > If you want something stable, I would suggest to follow this: > http://wiki.ekiga.org/index.php/SVN > (and use the gnome-2-24 instructions) > -- > _ Damien Sandras > (o- > //\\ Ekiga Softphone : http://www.ekiga.org/ > v_/_ Be IP : http://www.beip.be/ > FOSDEM : http://www.fosdem.org/ > SIP Phone : sip:dsandras at ekiga.net > > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list __________ Najpopul?rnej?? blog na Slovensku - http://blog.sme.sk/ From palos at post.sk Wed Dec 24 00:53:55 2008 From: palos at post.sk (Palo S.) Date: 24 Dec 2008 01:53:55 +0100 (CET) Subject: [Ekiga-list] 473 Filtered destination Message-ID: <49518823.000001.25844@kamasutra> Recently, it happened to me several times that I could not initialize a call although I knew for sure that the other side was online. Also, I got similar complaints from others not able to reach me by Ekiga but when they used eg Ekiga->my other SIP client they reached me fine. Sometimes (but not always) this problem was be fixed by restarting Ekiga on both sides, sometimes it fixed \"itself\" after some longer time... I managed to catch a d4 log from one of these cases: ftp://quacka.no-ip.org/pub/ekiga2.log It says that Kamailio returns \"473 Filtered destination (473/TM)\" to to the caller right after the caller sends INVITEs. Then the call fails with \"Local user cleared the call\". What does this filtered destination mean? Is Kamailio blacklisting the users from some reason? Palo __________ http://www.tahaj.sk - Stiahnite si najnovsie verzie vasich oblubenych programov From peasthope at shaw.ca Wed Dec 24 01:25:48 2008 From: peasthope at shaw.ca (peasthope at shaw.ca) Date: Tue, 23 Dec 2008 17:25:48 -0800 Subject: [Ekiga-list] Re (2): Re^3: Usage of Ekiga 3. Was "failure in registration of sip account". Message-ID: Folk, ds> Perhaps you should provide a -d4 output. Right oh. As luck has it, opening x-terminal-emulator on this system kills X. For terminal access I use telnet or ssh via the LAN. According to my understanding, Ekiga must be told the identity of the X display which is the machine console. The command will be similar to this. ekiga -d 4 -display ?? -c sip:12506291234 at sip.diamondcard.us /etc/X11/xorg.conf has these sections, Section "Device" Section "Monitor" Section "Screen" but no Section "Display" . How is the X display identified? Sorry; I've never needed this till now. I might be off line for a few days but will collect the debug output a soon as possible. Regards, ... Peter E. -- http://members.shaw.ca/peasthope/ http://carnot.yi.org/ = http://carnot.pathology.ubc.ca/ From dsandras at seconix.com Wed Dec 24 08:41:59 2008 From: dsandras at seconix.com (Damien Sandras) Date: Wed, 24 Dec 2008 09:41:59 +0100 Subject: [Ekiga-list] Trouble getting cross-plattform video to work In-Reply-To: <1230076937.10105.100.camel@achille> References: <49516599.5040807@eBiology.de> <1230071762.10105.90.camel@achille> <495170D7.3020401@eBiology.de> <1230076284.10105.96.camel@achille> <1230076937.10105.100.camel@achille> Message-ID: <1230108119.20691.1.camel@scorpion.multitel.be> Le mercredi 24 d?cembre 2008 ? 01:02 +0100, yannick a ?crit : > Le mercredi 24 d?cembre 2008 ? 00:51 +0100, yannick a ?crit : > > Le mercredi 24 d?cembre 2008 ? 00:14 +0100, Torsten Crass a ?crit : > > > both clients are sitting behind the same router > > > > That might explain your trouble, the test ekiga use to get your internet > > IP might confuse the 2 clients as they have the same public IP. The best > > I can think of is try to setup bonjour for windows > > http://support.apple.com/downloads/Bonjour_for_Windows > > > > Then clients should automatically appears in the roster. > > > > Damien, if i understand correctly the situation STUN gives both client > the same IP. When client A try to signaling with client B, ekiga.net > gives the IP of client B to client A; is there a test to check if both > IP are the the same to pop up an error message ? Maybe with a link to > our wiki? Is it worth to report feature request in bugzilla for this? > Unfortunately the PDU comes from ekiga.net. Perhaps we might check the contact field, but that would be overly complex. The problem is due to routers that are unable to route back the trafic inside the LAN when being addressed through their internal interface with an external address. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From dsandras at seconix.com Wed Dec 24 08:42:18 2008 From: dsandras at seconix.com (Damien Sandras) Date: Wed, 24 Dec 2008 09:42:18 +0100 Subject: [Ekiga-list] \"remote user cleared the call\" problem In-Reply-To: <49518195.000001.25125@kamasutra> References: <49518195.000001.25125@kamasutra> Message-ID: <1230108138.20691.3.camel@scorpion.multitel.be> Le mercredi 24 d?cembre 2008 ? 01:25 +0100, Palo S. a ?crit : > I can confirm that this problem is fixed. The call is not > canceled anymore (although I only tested via VNC ie nobody > on the other side so I cannot say whether there are some > other issues such as voice not coming through). > Good job! > Great! -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From dsandras at seconix.com Wed Dec 24 09:49:18 2008 From: dsandras at seconix.com (Damien Sandras) Date: Wed, 24 Dec 2008 10:49:18 +0100 Subject: [Ekiga-list] 473 Filtered destination In-Reply-To: <49518823.000001.25844@kamasutra> References: <49518823.000001.25844@kamasutra> Message-ID: <1230112158.20691.32.camel@scorpion.multitel.be> Le mercredi 24 d?cembre 2008 ? 01:53 +0100, Palo S. a ?crit : > Recently, it happened to me several times that I could not > initialize a call although I knew for sure that the other > side was online. Also, I got similar complaints from others > not able to reach me by Ekiga but when they used eg > Ekiga->my other SIP client they reached me fine. Sometimes > (but not always) this problem was be fixed by restarting > Ekiga on both sides, sometimes it fixed \"itself\" after > some longer time... > > I managed to catch a d4 log from one of these cases: > ftp://quacka.no-ip.org/pub/ekiga2.log > It says that Kamailio returns \"473 Filtered destination > (473/TM)\" to to the caller right after the caller sends > INVITEs. Then the call fails with \"Local user cleared > the call\". What does this filtered destination mean? > Is Kamailio blacklisting the users from some reason? http://lists.openser.org/pipermail/users/2008-March/016618.html This reply is internally generated by the blacklists core - the destination IP address was blacklisted (maybe due a 50x or timeout to previous response). This is a self-protection mechanism to prevent sending requests to destination already detected as unresponsive. I have disabled it. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From sevmek at free.fr Wed Dec 24 09:49:44 2008 From: sevmek at free.fr (yannick) Date: Wed, 24 Dec 2008 10:49:44 +0100 Subject: [Ekiga-list] Trouble getting cross-plattform video to work In-Reply-To: <1230076284.10105.96.camel@achille> References: <49516599.5040807@eBiology.de> <1230071762.10105.90.camel@achille> <495170D7.3020401@eBiology.de> <1230076284.10105.96.camel@achille> Message-ID: <1230112184.10105.103.camel@achille> Le mercredi 24 d?cembre 2008 ? 00:51 +0100, yannick a ?crit : > Le mercredi 24 d?cembre 2008 ? 00:14 +0100, Torsten Crass a ?crit : > > both clients are sitting behind the same router > > That might explain your trouble, the test ekiga use to get your internet > IP might confuse the 2 clients as they have the same public IP. The best > I can think of is try to setup bonjour for windows > http://support.apple.com/downloads/Bonjour_for_Windows > > Then clients should automatically appears in the roster. > To clarify my point: If your ekigas were not on the same LAN, it would have work as it work for me and my friend. Installing bonjour on the windows platform will make it work inside your LAN. > Best regards, > Yannick > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list -- Me joindre en t?l?phonie IP / vid?oconf?rence ? sip:yannick at ekiga.net Logiciel de VoIP Ekiga : http://www.ekiga.org http://wiki.ekiga.org/index.php/Which_programs_work_with_Ekiga_%3F From torsten.crass at eBiology.de Wed Dec 24 12:49:10 2008 From: torsten.crass at eBiology.de (Torsten Crass) Date: Wed, 24 Dec 2008 13:49:10 +0100 Subject: [Ekiga-list] Trouble getting cross-plattform video to work In-Reply-To: <1230112184.10105.103.camel@achille> References: <49516599.5040807@eBiology.de> <1230071762.10105.90.camel@achille> <495170D7.3020401@eBiology.de> <1230076284.10105.96.camel@achille> <1230112184.10105.103.camel@achille> Message-ID: <49522FC6.3080704@eBiology.de> Yannick (and others), > If your ekigas were not on the same LAN, it would have work as it work > for me and my friend. Installing bonjour on the windows platform will > make it work inside your LAN. I see... ok, but since my current setup (both Linux and Windows behind the same NAT router) was supposed to serve testing purposes only and the target scenario will encompass two separate LANs, I don't think I should like installing bonjour on the Windows machine. This morning I tried to connect to our home LAN (the Windows client) from my sister-in-law's place (hooked up my Linux laptop to their DSL router (128 kBit/s upstream)) -- just to experience some new problems preventing me from successfully "phoning home". The first issue seemed to have been related to NAT stuff (again) -- my relatives' router (a German T-Online Speedport W700V) "successfully" blocked my attempts to even register with ekiga.net; registration was possible only after completely disabling the built-in firewall. I wonder which wicked things this router was trying to do -- instead of just translating my datagrams' addresses to and fro. (Anybody else out there having trouble with Speeport routers...? Models W770V and W500 (without "V") in particular) But even after disabling the firewall and successful registration (here comes the 2nd problem) neither audio nor video was transmitted when trying out ekiga.net's echo service. :-( Dammit, I'd really love to see an idiot-proof open-protocoll-based open-source alternative to the "Microsoft of internet telephony", as one might call Skype... So if anyone had some idea on how to deal with the above mentioned issues, I'd be glad... Or maybe some debug info (yes, meanwhile I learned how to make Ekiga talk... :-) would be helpful? But anyway... top priority these day is, of course, celebrating Christmas with your loved ones (at least if you adhere to the underlying belief system ;-) So enjoy the day -- Torsten From sevmek at free.fr Wed Dec 24 13:59:25 2008 From: sevmek at free.fr (yannick) Date: Wed, 24 Dec 2008 14:59:25 +0100 Subject: [Ekiga-list] Trouble getting cross-plattform video to work In-Reply-To: <49522FC6.3080704@eBiology.de> References: <49516599.5040807@eBiology.de> <1230071762.10105.90.camel@achille> <495170D7.3020401@eBiology.de> <1230076284.10105.96.camel@achille> <1230112184.10105.103.camel@achille> <49522FC6.3080704@eBiology.de> Message-ID: <1230127165.10105.130.camel@achille> Le mercredi 24 d?cembre 2008 ? 13:49 +0100, Torsten Crass a ?crit : > The first issue seemed > to have been related to NAT stuff (again) -- my relatives' router (a > German T-Online Speedport W700V) "successfully" blocked my attempts > to > even register with ekiga.net; registration was possible only after > completely disabling the built-in firewall. I wonder which wicked > things > this router was trying to do -- instead of just translating my > datagrams' addresses to and fro. (Anybody else out there having > trouble > with Speeport routers...? Models W770V and W500 (without "V") in > particular) > > But even after disabling the firewall and successful registration > (here > comes the 2nd problem) neither audio nor video was transmitted when > trying out ekiga.net's echo service. :-( > After some googling, it seems quite clear to me this router ( Speedport W770V ) tries to help ekiga, and doing so it confuse it. Almost all the interesting pages are in german, I wont be able to help further configuring this router, but here is one good exemple of this router dealing with the SIP protocol: http://www.sipload.de/hilfe/inst_speed.php As Ekiga and the router try to both deal with SIP at the same time but are not able to coordinate the effort, the result is a failure. This issue, the lack of communication about the network topology between the end-point (the ekiga softphone) and the router is a general issue for the internet. There is people working on to solve it in the internet standardisation field. ICE looks very promising: http://tools.ietf.org/html/draft-ietf-mmusic-ice-19 Still there is no such standard at the moment. As a result, some router designer feels free to add or not support for SIP and they mostly do it there own way. It can be good reasons to implement SIP support in the router, as it seems the best spot in the LAN to deal with the internet, IPs, ports etc. Maybe it will add some benefits with this router (e.g. prioritising VoIP over other connections like games). Thus you have to manually configure either Ekiga, either the router, maybe both. In Ekiga you can disable the STUN support, as descibed in this feature request (there is no option to do so in ekiga 3.0.x): http://bugzilla.gnome.org/show_bug.cgi?id=562347 But as it is the windows version, you'll find this configuration in a file probably located here: C:\Documents and Settings\YOUR LOGIN\Applications Data\ekiga.conf The key should be something like: general/nat/method, and you probably needs to turn it to 0 to disable STUN support (i'm not really sure, as i get this information from the linux version...) Maybe this operation will be enough to get ekiga working on windows with this router, maybe you'll need to configure the router too. I cannot help for this step :( > Dammit, I'd really love to see an idiot-proof open-protocoll-based > open-source alternative to the "Microsoft of internet telephony", as > one > might call Skype... > Skype face exactly the same situation (except for the skype support in routers which seems very unlikely as the protocol is closed) and it deals with it using as many tricks it can, relaying on a peer-to-peer internet subnetwork. This way of doing things is a MAJOR trouble for security concerns and is against a healthy internet. Still it works in most cases... > So if anyone had some idea on how to deal with the above mentioned > issues, I'd be glad... Or maybe some debug info (yes, meanwhile I > learned how to make Ekiga talk... :-) would be helpful? I hope this will help. Best regards, Yannick From palos at post.sk Wed Dec 24 21:19:10 2008 From: palos at post.sk (Palo S.) Date: 24 Dec 2008 22:19:10 +0100 (CET) Subject: [Ekiga-list] 473 Filtered destination Message-ID: <4952A74E.000001.00352@kamasutra> > > http://lists.openser.org/pipermail/users/2008-March/016618.html > > This reply is internally generated by the blacklists core - the > destination IP address was blacklisted (maybe due a 50x or timeout > to previous response). This is a self-protection mechanism to prevent > sending requests to destination already detected as unresponsive. > > I have disabled it. Great, thanks! So one reason of the inability to make calls should be gone now, however doing today\'s Christmas calls, I found myself again not able to make a call and this time Kamailio returned \"480 Offline\" (repeatedly). I am sure though that the other side was online and registered because I again watched it via VNC. I have the logfile from the caller but I was not able to say more from it: ftp://quacka.no-ip.org/pub/ekiga.log Maybe a log from the called side would say more but I don\'t have that. The problem was fixed by restarting Ekiga on both sides... At least one thing makes sense now: I mentioned that sometimes restart of Ekiga fixes the problem and sometimes not - then it disappears by itself after some time. Now it becomes very likely that the former corresponds to 480 Offline and the latter to 473 Filtered destination (from openSER list I found that once blacklisted, the server always returns 473 for limited amount of time) 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:dsandras at ekiga.net > > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list __________ Mobiln? telef?ny v slovenskej premi?re a najaktu?lnej?ie inform?cie - http://mobil.sme.sk/ From fshock at hotmail.com Wed Dec 24 21:50:51 2008 From: fshock at hotmail.com (FS Inc.) Date: Wed, 24 Dec 2008 21:50:51 +0000 Subject: [Ekiga-list] Unable to get incoming calls from sip provider ekiga.net set up on asterisk In-Reply-To: References: Message-ID: *bump*From: fshock at hotmail.comTo: ekiga-list at gnome.orgDate: Thu, 18 Dec 2008 00:39:46 +0000Subject: [Ekiga-list] Unable to get incoming calls from sip provider ekiga.net set up on asterisk I've been using the wiki as a guide here...http://wiki.ekiga.org/index.php/Connecting_Asterisk_to_ekiga.netI've also tried various permutations, combinations and contortions but nada.below is my extensions.conf***** begin extensions.conf ****[general]static = yeswriteprotect = noautofallthrough = yesclearglobalvars = no[globals]CONSOLE = Console/dsp ; Console interface for demo;CONSOLE=Zap/1;CONSOLE=Phone/phone0IAXINFO = guest ; IAXtel username/password;IAXINFO=myuser:mypassTRUNK = Zap/G2 ; Trunk interfaceTRUNKMSD = 1 ; MSD digits to strip (usually 1 or 0);TRUNK=IAX2/user:pass at provider[default]exten => s,1,Verbose(1|Unrouted call handler)exten => s,n,Answer()exten => s,n,Wait(1)exten => s,n,Playback(tt-weasels)exten => s,n,Hangup()[macro-voicemail]exten => s,1,Dial(${ARG1},20)exten => s,n,Goto(s-${DIALSTATUS},1)exten => s-NOANSWER,1,Voicemail(u${MACRO_EXTEN})exten => s-NOANSWER,n,Hangup()exten => s-BUSY,1,Voicemail(b${MACRO_EXTEN})exten => s-BUSY,n,Hangup()exten => _s-.,1,Goto(s-NOANSWER,1)[incoming_calls]exten => ekiga_meyamma_in,1,Macro(voicemail,SIP/101)exten => ekiga_meyamma_in,n,Hangup()[internal_calls]exten => 101,1,Macro(voicemail,SIP/101)exten => 101,n,Hangup()exten => 102,1,Dial(SIP/102)exten => 102,n,Hangup()exten => 8,1,VoiceMailMain(s${CALLERIDNUM})exten => 8,n,Hangup()exten => 600,1,Answer()exten => 600,n,Playback(demo-echotest)exten => 600,n,Echo()exten => 600,n,Playback(demo-echodone)exten => 600,n,Hangup()[outgoing_calls]exten => _9.,1,Dial(SIP/ekiga_meyamma_out/${EXTEN:1},20,r))exten => _9.,n,Hangup()[home]include => internal_callsinclude => outgoing_calls***** end extensions.conf ****below is my sip.conf**** begin sip.conf ***[general]context=default bindport=5060 bindaddr=0.0.0.0 srvlookup=yes disallow=all allow=ulaw allow=alawallow=ilbc allow=gsmallow=h261videosupport=yes ; Register 2345 at sip provider 'sip_proxy'. Calls from this provider; connect to local extension 1234 in extensions.conf, default context,; unless you configure a [sip_proxy] section below, and configure a; context.; Tip 1: Avoid assigning hostname to a sip.conf section like [provider.com]; Tip 2: Use separate type=peer and type=user sections for SIP providers; (instead of type=friend) if you have calls in both directionsregister => meyamma:meyamma at ekiga.net/ekiga_meyamma_inexternhost=fspublic.selfip.com externrefresh=10 ;localnet=192.168.1.0/255.255.255.0[authentication];setup[101]type=friendusername=101secret=welcomequalify=yes nat=no host=dynamic canreinvite=no context=home;port=5061 ;setup[102]type=friendusername=102secret=welcomequalify=yes nat=no host=dynamic canreinvite=no context=home;port=5061 ;ekiga.net[ekiga_meyamma_out]type=peerusername=meyammasecret=meyammahost=ekiga.netcanreinvite=noqualify=300insecure=port,invite;ekiga.net[ekiga_meyamma_in]type=userusername=meyammasecret=meyammahost=ekiga.netcanreinvite=noqualify=300context=incoming_callsinsecure=port,invite**** end sip.conf ****These are the latest incantations of my sip and extensions conf files. Can anyone assist in helping me to get incoming calls from ekiga.net set up. I have the outgoing working as that was the simple part. That one is handled by [ekiga_meyamma_out] and [outgoing_calls].Thanks a milExplore the seven wonders of the world Learn more! _________________________________________________________________ More than messages?check out the rest of the Windows Live?. http://www.microsoft.com/windows/windowslive/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From afb at paradise.net.nz Thu Dec 25 08:46:49 2008 From: afb at paradise.net.nz (Adam Bogacki) Date: Thu, 25 Dec 2008 21:46:49 +1300 Subject: [Ekiga-list] Ekiga WiFi config ? Message-ID: <20081225084648.GB7446@paradise.net.nz> Hi, I have (inherited) a windows XP based laptop connected via WiFi to a router also feeding my desktop. I installed the latest Ekiga image but found there were no config options for WiFi. Is this a serious consideration in the near future ? Regards, Adam Bogacki, afb at paradise.net.nz -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: Digital signature URL: From torsten.crass at eBiology.de Thu Dec 25 10:29:26 2008 From: torsten.crass at eBiology.de (Torsten Crass) Date: Thu, 25 Dec 2008 11:29:26 +0100 Subject: [Ekiga-list] Trouble getting cross-plattform video to work In-Reply-To: <1230127165.10105.130.camel@achille> References: <49516599.5040807@eBiology.de> <1230071762.10105.90.camel@achille> <495170D7.3020401@eBiology.de> <1230076284.10105.96.camel@achille> <1230112184.10105.103.camel@achille> <49522FC6.3080704@eBiology.de> <1230127165.10105.130.camel@achille> Message-ID: <49536086.2070501@eBiology.de> Yannick, > After some googling, it seems quite clear to me this router ( Speedport > W770V ) tries to help ekiga, and doing so it confuse it. > Almost all the interesting pages are in german, I wont be able to help > further configuring this router, but here is one good exemple of this > router dealing with the SIP protocol: > http://www.sipload.de/hilfe/inst_speed.php thank you *so* much -- I guess this information will help me a lot getting thing to work! (Shame on me I didn't find this and similar pages myself -- suppose I didn't because I always had "Ekiga" among my query terms, but the issues I encountered obviously were generally sip-related rather than being Ekiga-specific... Anyway, good to learn that I wasn't entirely stupid, but things are really a bit more complicated with Speedport routers!) [...] > I hope this will help. I'm confident it will -- thanks again! Hope you got many nice presents -- Torsten ------------------------------ Dr. rer. nat. Torsten Crass Biochemiker - Bioinformatiker Breite Lade 20 31275 Lehrte Tel. 05132/8219177 torsten.crass at eBiology.de http://www.tcrass.de From dsandras at seconix.com Thu Dec 25 10:52:11 2008 From: dsandras at seconix.com (Damien Sandras) Date: Thu, 25 Dec 2008 11:52:11 +0100 Subject: [Ekiga-list] 473 Filtered destination In-Reply-To: <4952A74E.000001.00352@kamasutra> References: <4952A74E.000001.00352@kamasutra> Message-ID: <1230202331.20691.106.camel@scorpion.multitel.be> Le mercredi 24 d?cembre 2008 ? 22:19 +0100, Palo S. a ?crit : > > > > > http://lists.openser.org/pipermail/users/2008-March/016618.html > > > > This reply is internally generated by the blacklists core - the > > destination IP address was blacklisted (maybe due a 50x or timeout > > to previous response). This is a self-protection mechanism to prevent > > sending requests to destination already detected as unresponsive. > > > > I have disabled it. > > Great, thanks! So one reason of the inability to make calls > should be gone now, however doing today\'s Christmas calls, > I found myself again not able to make a call and this time > Kamailio returned \"480 Offline\" (repeatedly). I am sure > though that the other side was online and registered because > I again watched it via VNC. I have the logfile from the caller > but I was not able to say more from it: > ftp://quacka.no-ip.org/pub/ekiga.log > Maybe a log from the called side would say more but I don\'t > have that. The problem was fixed by restarting Ekiga on both > sides... Offline is sent back when the user is not in the database anymore. Perhaps it did not refresh the registration in time ? That is something you should look in his log : is there a REGISTER request to renew the registration or not. > At least one thing makes sense now: I mentioned that > sometimes restart of Ekiga fixes the problem and sometimes > not - then it disappears by itself after some time. > Now it becomes very likely that the former corresponds > to 480 Offline and the latter to 473 Filtered destination > (from openSER list I found that once blacklisted, the > server always returns 473 for limited amount of time) Yes, the behavior makes me things that the other side is going offline from time to time (from the server point of view). I really suspect a NAT issue or something similar. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From dsandras at seconix.com Thu Dec 25 10:53:02 2008 From: dsandras at seconix.com (Damien Sandras) Date: Thu, 25 Dec 2008 11:53:02 +0100 Subject: [Ekiga-list] Unable to get incoming calls from sip provider ekiga.net set up on asterisk In-Reply-To: References: Message-ID: <1230202382.20691.108.camel@scorpion.multitel.be> I suppose you should ask this question on the Asterisk mailing list ? Le mercredi 24 d?cembre 2008 ? 21:50 +0000, FS Inc. a ?crit : > *bump* > > > ______________________________________________________________________ > From: fshock at hotmail.com > To: ekiga-list at gnome.org > Date: Thu, 18 Dec 2008 00:39:46 +0000 > Subject: [Ekiga-list] Unable to get incoming calls from sip provider > ekiga.net set up on asterisk > > I've been using the wiki as a guide here... > > http://wiki.ekiga.org/index.php/Connecting_Asterisk_to_ekiga.net > > I've also tried various permutations, combinations and contortions but > nada. > > below is my extensions.conf > > ***** begin extensions.conf **** > [general] > static = yes > writeprotect = no > autofallthrough = yes > clearglobalvars = no > > [globals] > CONSOLE = Console/dsp ; Console interface for demo > ;CONSOLE=Zap/1 > ;CONSOLE=Phone/phone0 > IAXINFO = guest ; IAXtel username/password > ;IAXINFO=myuser:mypass > TRUNK = Zap/G2 ; Trunk interface > TRUNKMSD = 1 ; MSD digits to strip (usually 1 or 0) > ;TRUNK=IAX2/user:pass at provider > > [default] > exten => s,1,Verbose(1|Unrouted call handler) > exten => s,n,Answer() > exten => s,n,Wait(1) > exten => s,n,Playback(tt-weasels) > exten => s,n,Hangup() > > [macro-voicemail] > exten => s,1,Dial(${ARG1},20) > exten => s,n,Goto(s-${DIALSTATUS},1) > exten => s-NOANSWER,1,Voicemail(u${MACRO_EXTEN}) > exten => s-NOANSWER,n,Hangup() > exten => s-BUSY,1,Voicemail(b${MACRO_EXTEN}) > exten => s-BUSY,n,Hangup() > exten => _s-.,1,Goto(s-NOANSWER,1) > > [incoming_calls] > exten => ekiga_meyamma_in,1,Macro(voicemail,SIP/101) > exten => ekiga_meyamma_in,n,Hangup() > > [internal_calls] > exten => 101,1,Macro(voicemail,SIP/101) > exten => 101,n,Hangup() > exten => 102,1,Dial(SIP/102) > exten => 102,n,Hangup() > exten => 8,1,VoiceMailMain(s${CALLERIDNUM}) > exten => 8,n,Hangup() > exten => 600,1,Answer() > exten => 600,n,Playback(demo-echotest) > exten => 600,n,Echo() > exten => 600,n,Playback(demo-echodone) > exten => 600,n,Hangup() > > [outgoing_calls] > exten => _9.,1,Dial(SIP/ekiga_meyamma_out/${EXTEN:1},20,r)) > exten => _9.,n,Hangup() > > [home] > include => internal_calls > include => outgoing_calls > ***** end extensions.conf **** > > below is my sip.conf > > **** begin sip.conf *** > [general] > context=default > bindport=5060 > > bindaddr=0.0.0.0 > srvlookup=yes > > disallow=all > allow=ulaw > allow=alaw > allow=ilbc > allow=gsm > allow=h261 > > videosupport=yes > > ; Register 2345 at sip provider 'sip_proxy'. Calls from this > provider > ; connect to local extension 1234 in extensions.conf, default > context, > ; unless you configure a [sip_proxy] section below, and configure a > ; context. > ; Tip 1: Avoid assigning hostname to a sip.conf section like > [provider.com] > ; Tip 2: Use separate type=peer and type=user sections for SIP > providers > ; (instead of type=friend) if you have calls in both > directions > register => meyamma:meyamma at ekiga.net/ekiga_meyamma_in > > externhost=fspublic.selfip.com > externrefresh=10 ; > localnet=192.168.1.0/255.255.255.0 > > [authentication] > > > ;setup > [101] > type=friend > username=101 > secret=welcome > qualify=yes > nat=no > host=dynamic > canreinvite=no > context=home > ;port=5061 > > ;setup > [102] > type=friend > username=102 > secret=welcome > qualify=yes > nat=no > host=dynamic > canreinvite=no > context=home > ;port=5061 > > ;ekiga.net > [ekiga_meyamma_out] > type=peer > username=meyamma > secret=meyamma > host=ekiga.net > canreinvite=no > qualify=300 > insecure=port,invite > > ;ekiga.net > [ekiga_meyamma_in] > type=user > username=meyamma > secret=meyamma > host=ekiga.net > canreinvite=no > qualify=300 > context=incoming_calls > insecure=port,invite > **** end sip.conf **** > > These are the latest incantations of my sip and extensions conf files. > Can anyone assist in helping me to get incoming calls from ekiga.net > set up. I have the outgoing working as that was the simple part. > That one is handled by [ekiga_meyamma_out] and [outgoing_calls]. > > Thanks a mil > > > ______________________________________________________________________ > Explore the seven wonders of the world Learn more! > > ______________________________________________________________________ > check out the rest of the Windows Live?. More than mail?Windows Live? > goes way beyond your inbox. More than messages > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From dsandras at seconix.com Thu Dec 25 10:53:39 2008 From: dsandras at seconix.com (Damien Sandras) Date: Thu, 25 Dec 2008 11:53:39 +0100 Subject: [Ekiga-list] Ekiga WiFi config ? In-Reply-To: <20081225084648.GB7446@paradise.net.nz> References: <20081225084648.GB7446@paradise.net.nz> Message-ID: <1230202419.20691.110.camel@scorpion.multitel.be> Le jeudi 25 d?cembre 2008 ? 21:46 +1300, Adam Bogacki a ?crit : > Hi, > > I have (inherited) a windows XP based laptop connected via > WiFi to a router also feeding my desktop. > > I installed the latest Ekiga image but found there were no > config options for WiFi. > > Is this a serious consideration in the near future ? What kind of wifi config options do you have in mind ? -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From Eugen.Dedu at pu-pm.univ-fcomte.fr Thu Dec 25 11:23:51 2008 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Thu, 25 Dec 2008 12:23:51 +0100 Subject: [Ekiga-list] Ekiga WiFi config ? In-Reply-To: <20081225084648.GB7446@paradise.net.nz> References: <20081225084648.GB7446@paradise.net.nz> Message-ID: <49536D47.80003@pu-pm.univ-fcomte.fr> Adam Bogacki wrote: > Hi, > > I have (inherited) a windows XP based laptop connected via > WiFi to a router also feeding my desktop. > > I installed the latest Ekiga image but found there were no > config options for WiFi. What config options do you think about? -- Eugen From palos at post.sk Thu Dec 25 15:13:13 2008 From: palos at post.sk (Palo S.) Date: 25 Dec 2008 16:13:13 +0100 (CET) Subject: [Ekiga-list] 473 Filtered destination Message-ID: <4953A309.000001.12348@kamasutra> > > Offline is sent back when the user is not in the database anymore. > Perhaps it did not refresh the registration in time ? That is something > you should look in his log : is there a REGISTER request to renew the > registration or not. I do not have a log from the other side, maybe I will succeed to reproduce the problem and get his log later. However, I am wondering now. How often should the registration renewing happen? I just looked to my current Ekiga log and there is absolutely no message between 4:47 till 14:13. And the 14:13 message only appeared because I wanted to close Ekiga - which did not succeed (it hanged, I had to kill it). I don\'t know whether this is related to the issue we have in this thread... anyway the log is here (although I don\'t think it says much, I cut it to the last 100 lines) ftp://quacka.no-ip.org/pub/ekiga_last100.log Palo __________ http://www.tahaj.sk - Stiahnite si najnovsie verzie vasich oblubenych programov From miguel203 at yahoo.com Thu Dec 25 15:41:00 2008 From: miguel203 at yahoo.com (Lebron Angel) Date: Thu, 25 Dec 2008 07:41:00 -0800 (PST) Subject: [Ekiga-list] Trouble getting cross-plattform video to work In-Reply-To: <1230076937.10105.100.camel@achille> Message-ID: <984198.5585.qm@web110304.mail.gq1.yahoo.com> take me out off the list. thank you happy holydays!!!! --- On Tue, 12/23/08, yannick wrote: From: yannick Subject: Re: [Ekiga-list] Trouble getting cross-plattform video to work To: "Ekiga mailing list" Date: Tuesday, December 23, 2008, 7:02 PM Le mercredi 24 d?cembre 2008 ? 00:51 +0100, yannick a ?crit : > Le mercredi 24 d?cembre 2008 ? 00:14 +0100, Torsten Crass a ?crit : > > both clients are sitting behind the same router > > That might explain your trouble, the test ekiga use to get your internet > IP might confuse the 2 clients as they have the same public IP. The best > I can think of is try to setup bonjour for windows > http://support.apple.com/downloads/Bonjour_for_Windows > > Then clients should automatically appears in the roster. > Damien, if i understand correctly the situation STUN gives both client the same IP. When client A try to signaling with client B, ekiga.net gives the IP of client B to client A; is there a test to check if both IP are the the same to pop up an error message ? Maybe with a link to our wiki? Is it worth to report feature request in bugzilla for this? > Best regards, > Yannick -- Me joindre en t?l?phonie IP / vid?oconf?rence ? sip:yannick at ekiga.net Logiciel de VoIP Ekiga : http://www.ekiga.org http://wiki.ekiga.org/index.php/Which_programs_work_with_Ekiga_%3F _______________________________________________ ekiga-list mailing list ekiga-list at gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list -------------- next part -------------- An HTML attachment was scrubbed... URL: From fshock at hotmail.com Thu Dec 25 15:58:37 2008 From: fshock at hotmail.com (FS Inc.) Date: Thu, 25 Dec 2008 15:58:37 +0000 Subject: [Ekiga-list] Unable to get incoming calls from sip provider ekiga.net set up on asterisk In-Reply-To: <1230202382.20691.108.camel@scorpion.multitel.be> References: <1230202382.20691.108.camel@scorpion.multitel.be> Message-ID: Are you sure? As I am using the ekiga wiki examples, the incoming works as described but the outgoing is confusing to me as its not clear to follow the example in the outgoing section of the ekiga wiki help.> From: dsandras at seconix.com> To: ekiga-list at gnome.org> Date: Thu, 25 Dec 2008 11:53:02 +0100> Subject: Re: [Ekiga-list] Unable to get incoming calls from sip provider ekiga.net set up on asterisk> > I suppose you should ask this question on the Asterisk mailing list ?> > Le mercredi 24 d?cembre 2008 ? 21:50 +0000, FS Inc. a ?crit :> > *bump*> > > > > > ______________________________________________________________________> > From: fshock at hotmail.com> > To: ekiga-list at gnome.org> > Date: Thu, 18 Dec 2008 00:39:46 +0000> > Subject: [Ekiga-list] Unable to get incoming calls from sip provider> > ekiga.net set up on asterisk> > > > I've been using the wiki as a guide here...> > > > http://wiki.ekiga.org/index.php/Connecting_Asterisk_to_ekiga.net> > > > I've also tried various permutations, combinations and contortions but> > nada.> > > > below is my extensions.conf> > > > ***** begin extensions.conf ****> > [general]> > static = yes> > writeprotect = no> > autofallthrough = yes> > clearglobalvars = no> > > > [globals]> > CONSOLE = Console/dsp ; Console interface for demo> > ;CONSOLE=Zap/1> > ;CONSOLE=Phone/phone0> > IAXINFO = guest ; IAXtel username/password> > ;IAXINFO=myuser:mypass> > TRUNK = Zap/G2 ; Trunk interface> > TRUNKMSD = 1 ; MSD digits to strip (usually 1 or 0)> > ;TRUNK=IAX2/user:pass at provider> > > > [default]> > exten => s,1,Verbose(1|Unrouted call handler)> > exten => s,n,Answer()> > exten => s,n,Wait(1)> > exten => s,n,Playback(tt-weasels)> > exten => s,n,Hangup()> > > > [macro-voicemail]> > exten => s,1,Dial(${ARG1},20)> > exten => s,n,Goto(s-${DIALSTATUS},1)> > exten => s-NOANSWER,1,Voicemail(u${MACRO_EXTEN})> > exten => s-NOANSWER,n,Hangup()> > exten => s-BUSY,1,Voicemail(b${MACRO_EXTEN})> > exten => s-BUSY,n,Hangup()> > exten => _s-.,1,Goto(s-NOANSWER,1)> > > > [incoming_calls]> > exten => ekiga_meyamma_in,1,Macro(voicemail,SIP/101)> > exten => ekiga_meyamma_in,n,Hangup()> > > > [internal_calls]> > exten => 101,1,Macro(voicemail,SIP/101)> > exten => 101,n,Hangup()> > exten => 102,1,Dial(SIP/102)> > exten => 102,n,Hangup()> > exten => 8,1,VoiceMailMain(s${CALLERIDNUM})> > exten => 8,n,Hangup()> > exten => 600,1,Answer()> > exten => 600,n,Playback(demo-echotest)> > exten => 600,n,Echo()> > exten => 600,n,Playback(demo-echodone)> > exten => 600,n,Hangup()> > > > [outgoing_calls]> > exten => _9.,1,Dial(SIP/ekiga_meyamma_out/${EXTEN:1},20,r))> > exten => _9.,n,Hangup()> > > > [home]> > include => internal_calls> > include => outgoing_calls> > ***** end extensions.conf ****> > > > below is my sip.conf> > > > **** begin sip.conf ***> > [general]> > context=default > > bindport=5060 > > > > bindaddr=0.0.0.0 > > srvlookup=yes > > > > disallow=all > > allow=ulaw > > allow=alaw> > allow=ilbc > > allow=gsm> > allow=h261> > > > videosupport=yes > > > > ; Register 2345 at sip provider 'sip_proxy'. Calls from this> > provider> > ; connect to local extension 1234 in extensions.conf, default> > context,> > ; unless you configure a [sip_proxy] section below, and configure a> > ; context.> > ; Tip 1: Avoid assigning hostname to a sip.conf section like> > [provider.com]> > ; Tip 2: Use separate type=peer and type=user sections for SIP> > providers> > ; (instead of type=friend) if you have calls in both> > directions> > register => meyamma:meyamma at ekiga.net/ekiga_meyamma_in> > > > externhost=fspublic.selfip.com > > externrefresh=10 ;> > localnet=192.168.1.0/255.255.255.0> > > > [authentication]> > > > > > ;setup> > [101]> > type=friend> > username=101> > secret=welcome> > qualify=yes > > nat=no > > host=dynamic > > canreinvite=no > > context=home> > ;port=5061 > > > > ;setup> > [102]> > type=friend> > username=102> > secret=welcome> > qualify=yes > > nat=no > > host=dynamic > > canreinvite=no > > context=home> > ;port=5061 > > > > ;ekiga.net> > [ekiga_meyamma_out]> > type=peer> > username=meyamma> > secret=meyamma> > host=ekiga.net> > canreinvite=no> > qualify=300> > insecure=port,invite> > > > ;ekiga.net> > [ekiga_meyamma_in]> > type=user> > username=meyamma> > secret=meyamma> > host=ekiga.net> > canreinvite=no> > qualify=300> > context=incoming_calls> > insecure=port,invite> > **** end sip.conf ****> > > > These are the latest incantations of my sip and extensions conf files.> > Can anyone assist in helping me to get incoming calls from ekiga.net> > set up. I have the outgoing working as that was the simple part.> > That one is handled by [ekiga_meyamma_out] and [outgoing_calls].> > > > Thanks a mil> > > > > > ______________________________________________________________________> > Explore the seven wonders of the world Learn more!> > > > ______________________________________________________________________> > check out the rest of the Windows Live?. More than mail?Windows Live?> > goes way beyond your inbox. More than messages> > _______________________________________________> > ekiga-list mailing list> > ekiga-list at gnome.org> > http://mail.gnome.org/mailman/listinfo/ekiga-list> -- > _ Damien Sandras> (o- > //\ Ekiga Softphone : http://www.ekiga.org/> v_/_ Be IP : http://www.beip.be/> FOSDEM : http://www.fosdem.org/> SIP Phone : sip:dsandras at ekiga.net> > > _______________________________________________> ekiga-list mailing list> ekiga-list at gnome.org> http://mail.gnome.org/mailman/listinfo/ekiga-list _________________________________________________________________ Drag n? drop?Get easy photo sharing with Windows Live? Photos. http://www.microsoft.com/windows/windowslive/photos.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From liqlee at gmail.com Thu Dec 25 23:44:27 2008 From: liqlee at gmail.com (LiQun Li) Date: Thu, 25 Dec 2008 17:44:27 -0600 Subject: [Ekiga-list] Unable to get incoming calls from sip provider ekiga.net set up on asterisk In-Reply-To: References: <1230202382.20691.108.camel@scorpion.multitel.be> Message-ID: Hi, Since I read the manual of Ekiga, it is compatible to X-lite, I try to set it up to connect to freedigits.net. Edit --> Accounts : Account Name: whatever Registrar: freedigits.net User: yyyyyyyyyy // 10 digits phone number, got from freedigits.com Password: zzzz // password for Authentication login : yyyyyyyyyy Realm/Domain : freedigits.net Registration Timeout: 3600 but it can not connect to freedigits. I retrieve all old archives, I can not any posts related to the setting. Any suggestions or comments will be appreciated, From palos at post.sk Fri Dec 26 02:05:08 2008 From: palos at post.sk (Palo S.) Date: 26 Dec 2008 03:05:08 +0100 (CET) Subject: [Ekiga-list] 473 Filtered destination Message-ID: <49543BD4.000002.18845@kamasutra> > > I don\\\'t know whether this is related to the issue we > have in this thread... Now I know - it is related. It seems to be a pattern: After some time (seems to be around 1-2 hours from Ekiga start) there is no communication anymore between the client and the server. The client still claims it is registered and I can even make a call, however I am not reachable - the other side gets \"408 Request timeout\". Trying to quit the client causes a freeze then. It is 3.0.1 compiled from source. I will try to play with NAT settings when I have some time to see whether it is caused by that. Palo __________ Sprievodca hern?m svetom - http://hry.sme.sk/ From dsandras at seconix.com Fri Dec 26 08:49:29 2008 From: dsandras at seconix.com (Damien Sandras) Date: Fri, 26 Dec 2008 09:49:29 +0100 Subject: [Ekiga-list] 473 Filtered destination In-Reply-To: <4953A309.000001.12348@kamasutra> References: <4953A309.000001.12348@kamasutra> Message-ID: <1230281369.31287.11.camel@scorpion.multitel.be> Le jeudi 25 d?cembre 2008 ? 16:13 +0100, Palo S. a ?crit : > > > > Offline is sent back when the user is not in the database anymore. > > Perhaps it did not refresh the registration in time ? That is something > > you should look in his log : is there a REGISTER request to renew the > > registration or not. > > I do not have a log from the other side, maybe I will > succeed to reproduce the problem and get his log later. > > However, I am wondering now. How often should the > registration renewing happen? I just looked to my current > Ekiga log and there is absolutely no message between > 4:47 till 14:13. And the 14:13 message only appeared > because I wanted to close Ekiga - which did not succeed > (it hanged, I had to kill it). I don\'t know whether this > is related to the issue we have in this thread... anyway > the log is here (although I don\'t think it says much, I > cut it to the last 100 lines) > ftp://quacka.no-ip.org/pub/ekiga_last100.log > That's certainly the root cause of the problem. Can you try reproducing and providing a full log ? -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From dsandras at seconix.com Fri Dec 26 08:50:50 2008 From: dsandras at seconix.com (Damien Sandras) Date: Fri, 26 Dec 2008 09:50:50 +0100 Subject: [Ekiga-list] Unable to get incoming calls from sip provider ekiga.net set up on asterisk In-Reply-To: References: <1230202382.20691.108.camel@scorpion.multitel.be> Message-ID: <1230281450.31287.13.camel@scorpion.multitel.be> Le jeudi 25 d?cembre 2008 ? 15:58 +0000, FS Inc. a ?crit : > Are you sure? > As I am using the ekiga wiki examples, the incoming works as described > but the outgoing is confusing to me as its not clear to follow the > example in the outgoing section of the ekiga wiki help. Your problem is related to the asterisk syntax and dialplan, not to ekiga.net... At first sight, your example looks correct. So I would advise asking for help to the Asterisk experts. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From dsandras at seconix.com Fri Dec 26 08:51:09 2008 From: dsandras at seconix.com (Damien Sandras) Date: Fri, 26 Dec 2008 09:51:09 +0100 Subject: [Ekiga-list] Unable to get incoming calls from sip provider ekiga.net set up on asterisk In-Reply-To: References: <1230202382.20691.108.camel@scorpion.multitel.be> Message-ID: <1230281469.31287.15.camel@scorpion.multitel.be> Le jeudi 25 d?cembre 2008 ? 17:44 -0600, LiQun Li a ?crit : > Hi, > > Since I read the manual of Ekiga, it is compatible to X-lite, I try to > set it up to connect to freedigits.net. > Edit --> Accounts : > Account Name: whatever > Registrar: freedigits.net > User: yyyyyyyyyy // 10 digits phone number, got from freedigits.com > Password: zzzz // password for > > Authentication login : yyyyyyyyyy > Realm/Domain : freedigits.net > Registration Timeout: 3600 > > but it can not connect to freedigits. > I retrieve all old archives, I can not any posts related to the setting. > > Any suggestions or comments will be appreciated, That looks correct. Do you have a debug output ? -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From dsandras at seconix.com Fri Dec 26 08:51:37 2008 From: dsandras at seconix.com (Damien Sandras) Date: Fri, 26 Dec 2008 09:51:37 +0100 Subject: [Ekiga-list] 473 Filtered destination In-Reply-To: <49543BD4.000002.18845@kamasutra> References: <49543BD4.000002.18845@kamasutra> Message-ID: <1230281497.31287.17.camel@scorpion.multitel.be> Le vendredi 26 d?cembre 2008 ? 03:05 +0100, Palo S. a ?crit : > > > > > I don\\\'t know whether this is related to the issue we > > have in this thread... > > Now I know - it is related. It seems to be a pattern: > After some time (seems to be around 1-2 hours from Ekiga > start) there is no communication anymore between the > client and the server. The client still claims it is > registered and I can even make a call, however I am > not reachable - the other side gets \"408 Request > timeout\". Trying to quit the client causes a freeze > then. It is 3.0.1 compiled from source. > > I will try to play with NAT settings when I have some > time to see whether it is caused by that. > See my answer above. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From palos at post.sk Fri Dec 26 11:01:06 2008 From: palos at post.sk (Palo S.) Date: 26 Dec 2008 12:01:06 +0100 (CET) Subject: [Ekiga-list] 473 Filtered destination Message-ID: <4954B972.000001.02093@kamasutra> The complete log is here: ftp://quacka.no-ip.org/pub/ekiga-problem.log There is no call at the end I tried to close Ekiga and then had to kill it. (I also tried to call to the client but there is nothing about it in the log, the server returned 408 Request Timeout.) Palo __________ http://auto.sme.sk - V?etko o aut?ch (novinky, testy, autosal?n, auto?kola, porovnaj si auto) From dsandras at seconix.com Fri Dec 26 11:27:33 2008 From: dsandras at seconix.com (Damien Sandras) Date: Fri, 26 Dec 2008 12:27:33 +0100 Subject: [Ekiga-list] 473 Filtered destination In-Reply-To: <4954B972.000001.02093@kamasutra> References: <4954B972.000001.02093@kamasutra> Message-ID: <1230290853.31287.36.camel@scorpion.multitel.be> Le vendredi 26 d?cembre 2008 ? 12:01 +0100, Palo S. a ?crit : > The complete log is here: > ftp://quacka.no-ip.org/pub/ekiga-problem.log > > There is no call at the end I tried to close > Ekiga and then had to kill it. (I also tried to > call to the client but there is nothing about > it in the log, the server returned 408 Request > Timeout.) You set the registration time to 36 000 seconds in the account definition. It means 10 hours. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From dsandras at seconix.com Fri Dec 26 12:05:57 2008 From: dsandras at seconix.com (Damien Sandras) Date: Fri, 26 Dec 2008 13:05:57 +0100 Subject: [Ekiga-list] 473 Filtered destination In-Reply-To: <1230290853.31287.36.camel@scorpion.multitel.be> References: <4954B972.000001.02093@kamasutra> <1230290853.31287.36.camel@scorpion.multitel.be> Message-ID: <1230293157.31287.38.camel@scorpion.multitel.be> Le vendredi 26 d?cembre 2008 ? 12:27 +0100, Damien Sandras a ?crit : > Le vendredi 26 d?cembre 2008 ? 12:01 +0100, Palo S. a ?crit : > > The complete log is here: > > ftp://quacka.no-ip.org/pub/ekiga-problem.log > > > > There is no call at the end I tried to close > > Ekiga and then had to kill it. (I also tried to > > call to the client but there is nothing about > > it in the log, the server returned 408 Request > > Timeout.) > > You set the registration time to 36 000 seconds in the account > definition. It means 10 hours. I have limited it to 20 minutes max and 10 minutes min at the Ekiga.net level => it should not accept 10 hours anymore. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From palos at post.sk Fri Dec 26 14:43:16 2008 From: palos at post.sk (Palo S.) Date: 26 Dec 2008 15:43:16 +0100 (CET) Subject: [Ekiga-list] 473 Filtered destination Message-ID: <4954ED84.000001.18056@kamasutra> > > You set the registration time to 36 000 seconds in the account > definition. It means 10 hours. I can\'t remember setting that but it is so indeed... > I have limited it to 20 minutes max and 10 minutes min at > the Ekiga.net level => it should not accept 10 hours anymore. Did not help, still the same behaviour. I will set it to 3600 in the client and we shall see... Palo __________ Najoriginalnejsie technologicke hracky - http://pocitace.sme.sk/ From palos at post.sk Fri Dec 26 15:01:40 2008 From: palos at post.sk (Palo S.) Date: 26 Dec 2008 16:01:40 +0100 (CET) Subject: [Ekiga-list] 473 Filtered destination Message-ID: <4954F1D4.000001.19396@kamasutra> > I will set it to 3600 in the client and we shall see... I set it to 3600 in gconf (sip:registrar_registration_timeout as well as in accounts_list) but it seems that both settings are ignored? The log still says 36000. Is there a separate settings at ekiga.net? Is there a way for me to set it? Palo __________ http://sport.sme.sk - Najkomplexnej?ie inform?cie zo ?portu From palos at post.sk Fri Dec 26 23:06:08 2008 From: palos at post.sk (Palo S.) Date: 27 Dec 2008 00:06:08 +0100 (CET) Subject: [Ekiga-list] 473 Filtered destination Message-ID: <49556360.000002.20513@kamasutra> > I set it to 3600 in gconf > (sip:registrar_registration_timeout as well as in > accounts_list) but it seems that both settings are > ignored? The log still says 36000. Is there a > separate settings at ekiga.net? Is there a way > for me to set it? > Sorry for my monologue... It turned out that the gconf settings were applied with delay. I tried both 3600 and 600 but the problem persists with the same behaviour - all communication is halted after some time. The network consists of Zyxel ADSL modem bridged to WRT54GL router running Tomato firmware. Using or not using port forwarding does not play a role either. Full log using registration time of 600 is here: ftp://quacka.no-ip.org/pub/ekiga.log.7z (.tgz is available at the same location if preferred) It could still be a NAT issue but it would be bit weird because there is a SIP hardphone connected to the same router and it works without any problems with two SIP (non-Ekiga) accounts... so I really don\'t know what is going on here at the moment! Palo __________ http://www.pnp.sk - pridajte svoje fotky na PaciNepaci From bnc at astronomicalresearchaustralia.org Sat Dec 27 01:30:39 2008 From: bnc at astronomicalresearchaustralia.org (Brian) Date: Sat, 27 Dec 2008 11:30:39 +1000 Subject: [Ekiga-list] Compile Problem In-Reply-To: <49556360.000002.20513@kamasutra> References: <49556360.000002.20513@kamasutra> Message-ID: <4955853F.4090407@astronomicalresearchaustralia.org> Hi, I am trying to compile ekiga 3.0.1 on a SUSE 11.1 system. I am not sure if there are two problems or they are related. 1) My configure comes up with configure:5040: gcc -E conftest.c conftest.c:14:28: error: ac_nonexistent.h: No such file or directory configure:5046: $? = 1 configure: failed program was: | /* confdefs.h. */ | #define PACKAGE_NAME "ekiga" | #define PACKAGE_TARNAME "ekiga" | #define PACKAGE_VERSION "3.0.1" | #define PACKAGE_STRING "ekiga 3.0.1" | #define PACKAGE_BUGREPORT "http://bugzilla.gnome.org/enter_bug.cgi?product=ekiga" | #define PACKAGE "ekiga" | #define VERSION "3.0.1" | #define MAJOR_VERSION 3 | #define MINOR_VERSION 0 | #define BUILD_TYPE ReleaseCode | #define BUILD_NUMBER 1 | /* end confdefs.h. */ | #include configure:5079: result: gcc -E configure:5108: gcc -E conftest.c configure:5114: $? = 0 configure:5145: gcc -E conftest.c conftest.c:14:28: error: ac_nonexistent.h: No such file or directory configure:5151: $? = 1 configure: failed program was: | /* confdefs.h. */ | #define PACKAGE_NAME "ekiga" | #define PACKAGE_TARNAME "ekiga" | #define PACKAGE_VERSION "3.0.1" | #define PACKAGE_STRING "ekiga 3.0.1" | #define PACKAGE_BUGREPORT "http://bugzilla.gnome.org/enter_bug.cgi?product=ekiga" | #define PACKAGE "ekiga" | #define VERSION "3.0.1" | #define MAJOR_VERSION 3 | #define MINOR_VERSION 0 | #define BUILD_TYPE ReleaseCode | #define BUILD_NUMBER 1 | /* end confdefs.h. */ 2) The make fails with libtool: link: cannot find the library `/usr/lib/gcc/i586-suse-linux/4.3/../../../libsigc-2.0.la' or unhandled argument `/usr/lib/gcc/i586-suse-linux/4.3/../../../libsigc-2.0.la' make[6]: *** [liblocal-roster.la] Error 1 make[6]: Leaving directory `/Documents/SOURCE/SUSE11/ekiga-3.0.1/lib/engine/presence/local-roster' make[5]: *** [all-recursive] Error 1 make[5]: Leaving directory `/Documents/SOURCE/SUSE11/ekiga-3.0.1/lib/engine/presence' make[4]: *** [all-recursive] Error 1 make[4]: Leaving directory `/Documents/SOURCE/SUSE11/ekiga-3.0.1/lib/engine' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/Documents/SOURCE/SUSE11/ekiga-3.0.1/lib' make[2]: *** [all] Error 2 make[2]: Leaving directory `/Documents/SOURCE/SUSE11/ekiga-3.0.1/lib' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/Documents/SOURCE/SUSE11/ekiga-3.0.1' make: *** [all] Error 2 I have libsigc(2.2.2-40.25) installed. /usr/lib/libsigc-2.0.so.0 /usr/lib/libsigc-2.0.so.0.0.0 Would I be better off trying to use the head version? If so what is the svn command for it? FYI, I tried to use the supplied ekiga from suse 11.1 but it would not give me the option to use a V4L2 camera. Also I nolonger get the option to do a test during the config wizard. Thanks, Brian From dsandras at seconix.com Sat Dec 27 10:14:23 2008 From: dsandras at seconix.com (Damien Sandras) Date: Sat, 27 Dec 2008 11:14:23 +0100 Subject: [Ekiga-list] 473 Filtered destination In-Reply-To: <49556360.000002.20513@kamasutra> References: <49556360.000002.20513@kamasutra> Message-ID: <1230372863.24875.4.camel@scorpion.multitel.be> Le samedi 27 d?cembre 2008 ? 00:06 +0100, Palo S. a ?crit : > > I set it to 3600 in gconf > > (sip:registrar_registration_timeout as well as in > > accounts_list) but it seems that both settings are > > ignored? The log still says 36000. Is there a > > separate settings at ekiga.net? Is there a way > > for me to set it? > > > > Sorry for my monologue... It turned out that the > gconf settings were applied with delay. I tried both > 3600 and 600 but the problem persists with the > same behaviour - all communication is halted after > some time. > > The network consists of Zyxel ADSL modem bridged to > WRT54GL router running Tomato firmware. Using or not > using port forwarding does not play a role either. > Full log using registration time of 600 is here: > ftp://quacka.no-ip.org/pub/ekiga.log.7z > (.tgz is available at the same location if preferred) > > It could still be a NAT issue but it would be bit weird > because there is a SIP hardphone connected to the same > router and it works without any problems with two SIP > (non-Ekiga) accounts... so I really don\'t know what is > going on here at the moment! Indeed, the problem is on Ekiga's side. At some point, it does not refresh the registration. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From dsandras at seconix.com Sat Dec 27 10:19:32 2008 From: dsandras at seconix.com (Damien Sandras) Date: Sat, 27 Dec 2008 11:19:32 +0100 Subject: [Ekiga-list] 473 Filtered destination In-Reply-To: <49556360.000002.20513@kamasutra> References: <49556360.000002.20513@kamasutra> Message-ID: <1230373172.24875.9.camel@scorpion.multitel.be> Le samedi 27 d?cembre 2008 ? 00:06 +0100, Palo S. a ?crit : > > I set it to 3600 in gconf > > (sip:registrar_registration_timeout as well as in > > accounts_list) but it seems that both settings are > > ignored? The log still says 36000. Is there a > > separate settings at ekiga.net? Is there a way > > for me to set it? > > > > Sorry for my monologue... It turned out that the > gconf settings were applied with delay. I tried both > 3600 and 600 but the problem persists with the > same behaviour - all communication is halted after > some time. > > The network consists of Zyxel ADSL modem bridged to > WRT54GL router running Tomato firmware. Using or not > using port forwarding does not play a role either. > Full log using registration time of 600 is here: > ftp://quacka.no-ip.org/pub/ekiga.log.7z > (.tgz is available at the same location if preferred) > > It could still be a NAT issue but it would be bit weird > because there is a SIP hardphone connected to the same > router and it works without any problems with two SIP > (non-Ekiga) accounts... so I really don\'t know what is > going on here at the moment! > Does TRUNK give the same problem ? -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From dsandras at seconix.com Sat Dec 27 10:29:12 2008 From: dsandras at seconix.com (Damien Sandras) Date: Sat, 27 Dec 2008 11:29:12 +0100 Subject: [Ekiga-list] Compile Problem In-Reply-To: <4955853F.4090407@astronomicalresearchaustralia.org> References: <49556360.000002.20513@kamasutra> <4955853F.4090407@astronomicalresearchaustralia.org> Message-ID: <1230373752.24875.14.camel@scorpion.multitel.be> Hi, Le samedi 27 d?cembre 2008 ? 11:30 +1000, Brian a ?crit : > Hi, > I am trying to compile ekiga 3.0.1 on a SUSE 11.1 system. > I am not sure if there are two problems or they are related. > > 1) My configure comes up with > > configure:5040: gcc -E conftest.c > conftest.c:14:28: error: ac_nonexistent.h: No such file or directory > configure:5046: $? = 1 > configure: failed program was: > | /* confdefs.h. */ > | #define PACKAGE_NAME "ekiga" > | #define PACKAGE_TARNAME "ekiga" > | #define PACKAGE_VERSION "3.0.1" > | #define PACKAGE_STRING "ekiga 3.0.1" > | #define PACKAGE_BUGREPORT > "http://bugzilla.gnome.org/enter_bug.cgi?product=ekiga" > | #define PACKAGE "ekiga" > | #define VERSION "3.0.1" > | #define MAJOR_VERSION 3 > | #define MINOR_VERSION 0 > | #define BUILD_TYPE ReleaseCode > | #define BUILD_NUMBER 1 > | /* end confdefs.h. */ > | #include > configure:5079: result: gcc -E > configure:5108: gcc -E conftest.c > configure:5114: $? = 0 > configure:5145: gcc -E conftest.c > conftest.c:14:28: error: ac_nonexistent.h: No such file or directory > configure:5151: $? = 1 > configure: failed program was: > | /* confdefs.h. */ > | #define PACKAGE_NAME "ekiga" > | #define PACKAGE_TARNAME "ekiga" > | #define PACKAGE_VERSION "3.0.1" > | #define PACKAGE_STRING "ekiga 3.0.1" > | #define PACKAGE_BUGREPORT > "http://bugzilla.gnome.org/enter_bug.cgi?product=ekiga" > | #define PACKAGE "ekiga" > | #define VERSION "3.0.1" > | #define MAJOR_VERSION 3 > | #define MINOR_VERSION 0 > | #define BUILD_TYPE ReleaseCode > | #define BUILD_NUMBER 1 > | /* end confdefs.h. */ Not sure what it means. > 2) The make fails with > libtool: link: cannot find the library > `/usr/lib/gcc/i586-suse-linux/4.3/../../../libsigc-2.0.la' or unhandled > argument `/usr/lib/gcc/i586-suse-linux/4.3/../../../libsigc-2.0.la' > make[6]: *** [liblocal-roster.la] Error 1 > make[6]: Leaving directory > `/Documents/SOURCE/SUSE11/ekiga-3.0.1/lib/engine/presence/local-roster' > make[5]: *** [all-recursive] Error 1 > make[5]: Leaving directory > `/Documents/SOURCE/SUSE11/ekiga-3.0.1/lib/engine/presence' > make[4]: *** [all-recursive] Error 1 > make[4]: Leaving directory `/Documents/SOURCE/SUSE11/ekiga-3.0.1/lib/engine' > make[3]: *** [all-recursive] Error 1 > make[3]: Leaving directory `/Documents/SOURCE/SUSE11/ekiga-3.0.1/lib' > make[2]: *** [all] Error 2 > make[2]: Leaving directory `/Documents/SOURCE/SUSE11/ekiga-3.0.1/lib' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/Documents/SOURCE/SUSE11/ekiga-3.0.1' > make: *** [all] Error 2 > Do you have the devel versions of libsigc++2 installed ? [...] > I tried to use the supplied ekiga from suse 11.1 but it would not give > me the option to use a V4L2 camera. I think there is a separate plugin. That is weird it is not installed by default, but go figure! > Also I nolonger get the option to do a test during the config wizard. It has been removed. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From bnc at astronomicalresearchaustralia.org Sat Dec 27 13:28:40 2008 From: bnc at astronomicalresearchaustralia.org (Brian) Date: Sat, 27 Dec 2008 23:28:40 +1000 Subject: [Ekiga-list] Compile Problem In-Reply-To: <1230373752.24875.14.camel@scorpion.multitel.be> References: <49556360.000002.20513@kamasutra> <4955853F.4090407@astronomicalresearchaustralia.org> <1230373752.24875.14.camel@scorpion.multitel.be> Message-ID: <49562D88.6090909@astronomicalresearchaustralia.org> Damien, Lets tackle one problem at a time:) >> argument `/usr/lib/gcc/i586-suse-linux/4.3/../../../libsigc-2.0.la' > Do you have the devel versions of libsigc++2 installed ? > Yes I do, the libsigc-2.0.la is not in it. However, I think this may be a package problem(don't quote me:) I did a search for libsigc-2.0.la across my whole system(I have a 10.0 a 10.3 and a 11.1 of suse) and it was only found in the old 10.0 system. So either I have not installed some gnome requirement or the file is no longer valid on newer systems. Then I noticed that this file is called by libtool. I had to install libtool on my system, but you have a shell script called libtool in the /ekiga-3.0.1 directory. I renamed this to see if it would pick up my system libtool and it said /bin/sh: ../../../../libtool: No such file or directory make[6]: *** [liblocal-roster.la] Error 127 make[6]: Leaving directory `/Documents/SOURCE/SUSE11/ekiga-3.0.1/lib/engine/presence/local-roster' etc. Which is correct as I had just renamed it. I guess my question is, should it be using my system libtool? If not what do I have to install to satisfy your libtool so that it can find libsigc-2.0.la, if it is still valid? BTW I am running the normal ./configure make with no flags on either Thanks, Brian From palos at post.sk Sat Dec 27 15:56:02 2008 From: palos at post.sk (Palo S.) Date: 27 Dec 2008 16:56:02 +0100 (CET) Subject: [Ekiga-list] 473 Filtered destination Message-ID: <49565012.000002.27428@kamasutra> > > Does TRUNK give the same problem ? The latest TRUNK segfaults right after start. Valgrind says ==27759== Invalid read of size 4 ==27759== at 0x819F0F0: Opal::Sip::EndPoint::EndPoint(Opal::CallManager&, Ekiga::ServiceCore&, unsigned) (sip-endpoint.cpp:131) ==27759== by 0x8163402: opal_init(Ekiga::ServiceCore&, int*, char***) (opal-main.cpp:117) ==27759== by 0x80F944B: engine_init(int, char**, Ekiga::Runtime*) (engine.cpp:222) ==27759== by 0x80E9BB1: GnomeMeeting::InitEngine() (ekiga.cpp:230) ==27759== by 0x80D6D09: main (main.cpp:4476) ==27759== Address 0x0 is not stack\'d, malloc\'d or (recently) free\'d ==27759== ==27759== Process terminating with default action of signal 11 (SIGSEGV) ==27759== Access not within mapped region at address 0x0 ==27759== at 0x819F0F0: Opal::Sip::EndPoint::EndPoint(Opal::CallManager&, Ekiga::ServiceCore&, unsigned) (sip-endpoint.cpp:131) ==27759== by 0x8163402: opal_init(Ekiga::ServiceCore&, int*, char***) (opal-main.cpp:117) ==27759== by 0x80F944B: engine_init(int, char**, Ekiga::Runtime*) (engine.cpp:222) ==27759== by 0x80E9BB1: GnomeMeeting::InitEngine() (ekiga.cpp:230) ==27759== by 0x80D6D09: main (main.cpp:4476) Palo __________ Najoriginalnejsie technologicke hracky - http://pocitace.sme.sk/ From dsandras at seconix.com Sat Dec 27 19:59:26 2008 From: dsandras at seconix.com (Damien Sandras) Date: Sat, 27 Dec 2008 20:59:26 +0100 Subject: [Ekiga-list] 473 Filtered destination In-Reply-To: <49565012.000002.27428@kamasutra> References: <49565012.000002.27428@kamasutra> Message-ID: <1230407966.24875.19.camel@scorpion.multitel.be> Le samedi 27 d?cembre 2008 ? 16:56 +0100, Palo S. a ?crit : > > > > Does TRUNK give the same problem ? > > The latest TRUNK segfaults right after start. > Valgrind says > > ==27759== Invalid read of size 4 > ==27759== at 0x819F0F0: Opal::Sip::EndPoint::EndPoint(Opal::CallManager&, Ekiga::ServiceCore&, unsigned) (sip-endpoint.cpp:131) > ==27759== by 0x8163402: opal_init(Ekiga::ServiceCore&, int*, char***) (opal-main.cpp:117) > ==27759== by 0x80F944B: engine_init(int, char**, Ekiga::Runtime*) (engine.cpp:222) > ==27759== by 0x80E9BB1: GnomeMeeting::InitEngine() (ekiga.cpp:230) > ==27759== by 0x80D6D09: main (main.cpp:4476) > ==27759== Address 0x0 is not stack\'d, malloc\'d or (recently) free\'d > ==27759== > ==27759== Process terminating with default action of signal 11 (SIGSEGV) > ==27759== Access not within mapped region at address 0x0 > ==27759== at 0x819F0F0: Opal::Sip::EndPoint::EndPoint(Opal::CallManager&, Ekiga::ServiceCore&, unsigned) (sip-endpoint.cpp:131) > ==27759== by 0x8163402: opal_init(Ekiga::ServiceCore&, int*, char***) (opal-main.cpp:117) > ==27759== by 0x80F944B: engine_init(int, char**, Ekiga::Runtime*) (engine.cpp:222) > ==27759== by 0x80E9BB1: GnomeMeeting::InitEngine() (ekiga.cpp:230) > ==27759== by 0x80D6D09: main (main.cpp:4476) Yes, that is a new problem that was introduced. I will fix that now, please try again in a few hours. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From dsandras at seconix.com Sat Dec 27 20:26:41 2008 From: dsandras at seconix.com (Damien Sandras) Date: Sat, 27 Dec 2008 21:26:41 +0100 Subject: [Ekiga-list] Compile Problem In-Reply-To: <49562D88.6090909@astronomicalresearchaustralia.org> References: <49556360.000002.20513@kamasutra> <4955853F.4090407@astronomicalresearchaustralia.org> <1230373752.24875.14.camel@scorpion.multitel.be> <49562D88.6090909@astronomicalresearchaustralia.org> Message-ID: <1230409601.30628.0.camel@scorpion.multitel.be> Le samedi 27 d?cembre 2008 ? 23:28 +1000, Brian a ?crit : > Damien, > Lets tackle one problem at a time:) > >> argument `/usr/lib/gcc/i586-suse-linux/4.3/../../../libsigc-2.0.la' > > > Do you have the devel versions of libsigc++2 installed ? > > > Yes I do, the libsigc-2.0.la is not in it. > However, I think this may be a package problem(don't quote me:) > > I did a search for libsigc-2.0.la across my whole system(I have a 10.0 a > 10.3 and a 11.1 of suse) and it was only found in the old 10.0 system. > So either I have not installed some gnome requirement or the file is no > longer valid on newer systems. > > Then I noticed that this file is called by libtool. > I had to install libtool on my system, but you have a shell script > called libtool in the /ekiga-3.0.1 directory. I renamed this to see if > it would pick up my system libtool and it said > > /bin/sh: ../../../../libtool: No such file or directory > make[6]: *** [liblocal-roster.la] Error 127 > make[6]: Leaving directory > `/Documents/SOURCE/SUSE11/ekiga-3.0.1/lib/engine/presence/local-roster' > > etc. > > Which is correct as I had just renamed it. > I guess my question is, should it be using my system libtool? > If not what do I have to install to satisfy your libtool so that it can > find libsigc-2.0.la, if it is still valid? I'm sorry, but I have no idea at all. Using libsigc-2.0.la does not look logical, I do not think it uses it here on Debian. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From liqlee at gmail.com Sun Dec 28 00:15:28 2008 From: liqlee at gmail.com (LiQun Li) Date: Sat, 27 Dec 2008 18:15:28 -0600 Subject: [Ekiga-list] Registration failed: Forbidden Message-ID: Hi, I try to set up Ekiga to connect freedigits.net. after setting up, it shows: Registration failed: Forbidden on its status bar. what does it mean? what should I do? thanks, From palos at post.sk Sun Dec 28 14:24:25 2008 From: palos at post.sk (Palo S.) Date: 28 Dec 2008 15:24:25 +0100 (CET) Subject: [Ekiga-list] 473 Filtered destination Message-ID: <49578C19.000001.27405@kamasutra> > > > > > > Does TRUNK give the same problem ? TRUNK gives the same problem. Furthermore I reproduced the same problem on two other computers: one in the same LAN and one in completely different network environment. Palo __________ http://sport.sme.sk - Najkomplexnej?ie inform?cie zo ?portu From f.vonbock at gmail.com Sun Dec 28 14:21:49 2008 From: f.vonbock at gmail.com (Fedor vonBock) Date: Sun, 28 Dec 2008 17:21:49 +0300 Subject: [Ekiga-list] could not register : behind a router In-Reply-To: <1229784717.27064.2.camel@scorpion.multitel.be> References: <1229373582.13601.45.camel@scorpion.multitel.be> <1229414703.13601.53.camel@scorpion.multitel.be> <4949063A.6070809@gmail.com> <1229542762.4276.8.camel@scorpion.multitel.be> <1229784717.27064.2.camel@scorpion.multitel.be> Message-ID: is it the network settings page on ekiga? there isn't one. I've enabled my PC (ubuntu hardy) to use a static ip address. how is the translation happening then? On Sat, Dec 20, 2008 at 5:51 PM, Damien Sandras wrote: > > 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:dsandras at ekiga.net > > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ji.cerny at gmail.com Sun Dec 28 14:56:47 2008 From: ji.cerny at gmail.com (Jiri Cerny) Date: Sun, 28 Dec 2008 15:56:47 +0100 Subject: [Ekiga-list] Problem connecting ekiga 3 to ekiga 2 Message-ID: <7ca14f9d0812280656u3a7d2e86o215437721b8a9ec0@mail.gmail.com> Recently I upgraded from Ekiga 2 to Ekiga 3 (by upgrading from Fedora 9 to Fedora 10). Since then I have problem to call my sister which still uses Ekiga 2 (more precisely quite old Ekiga 2.0.1 on Fedora Core 5, which cannot be upgraded easily). The problem is that she can hear me but I cannot hear her. When I reboot back to Fedora 9 and use Ekiga 2.0.12 (I think) to call her, then everything works fine, so there is not obvious problem with her setup. If I call 500 at ekiga.net from Ekiga 3.0, then everything is also fine. I have got logs from one unsuccessful call, but I do not understand them very well. They are attached to this email. Can you see from them, where the problem is? Thank for your help. Jiri -------------- next part -------------- A non-text attachment was scrubbed... Name: ekiga.2.log.gz Type: application/x-gzip Size: 8020 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ekiga.3.log.gz Type: application/x-gzip Size: 15401 bytes Desc: not available URL: From dsandras at seconix.com Sun Dec 28 18:07:58 2008 From: dsandras at seconix.com (Damien Sandras) Date: Sun, 28 Dec 2008 19:07:58 +0100 Subject: [Ekiga-list] Problem connecting ekiga 3 to ekiga 2 In-Reply-To: <7ca14f9d0812280656u3a7d2e86o215437721b8a9ec0@mail.gmail.com> References: <7ca14f9d0812280656u3a7d2e86o215437721b8a9ec0@mail.gmail.com> Message-ID: <1230487678.4343.9.camel@scorpion.multitel.be> Le dimanche 28 d?cembre 2008 ? 15:56 +0100, Jiri Cerny a ?crit : > Recently I upgraded from Ekiga 2 to Ekiga 3 (by upgrading from Fedora > 9 to Fedora 10). Since then I have problem to call my sister which > still uses Ekiga 2 (more precisely quite old Ekiga 2.0.1 on Fedora > Core 5, which cannot be upgraded easily). The problem is that she can > hear me but I cannot hear her. > > When I reboot back to Fedora 9 and use Ekiga 2.0.12 (I think) to call > her, then everything works fine, so there is not obvious problem with > her setup. If I call 500 at ekiga.net from Ekiga 3.0, then everything is > also fine. > > I have got logs from one unsuccessful call, but I do not understand > them very well. They are attached to this email. Can you see from > them, where the problem is? Thank for your help. There is something weird : it asks to receive audio on port 5062, it means that it is probably the same port on the router and on the desktop PC. However, it happens in both log, but in the Ekiga 3 log, you receive no audio. Can you check with tcpdump and / or wireshark if you actually receive something on port 5062 ? -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From dsandras at seconix.com Sun Dec 28 18:01:16 2008 From: dsandras at seconix.com (Damien Sandras) Date: Sun, 28 Dec 2008 19:01:16 +0100 Subject: [Ekiga-list] 473 Filtered destination In-Reply-To: <49578C19.000001.27405@kamasutra> References: <49578C19.000001.27405@kamasutra> Message-ID: <1230487276.4343.6.camel@scorpion.multitel.be> Le dimanche 28 d?cembre 2008 ? 15:24 +0100, Palo S. a ?crit : > > > > > > > > Does TRUNK give the same problem ? > > TRUNK gives the same problem. Furthermore I reproduced > the same problem on two other computers: one in the same > LAN and one in completely different network environment. > Are you talking about the REGISTER not being refreshed ? -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From dsandras at seconix.com Sun Dec 28 18:00:22 2008 From: dsandras at seconix.com (Damien Sandras) Date: Sun, 28 Dec 2008 19:00:22 +0100 Subject: [Ekiga-list] Registration failed: Forbidden In-Reply-To: References: Message-ID: <1230487222.4343.2.camel@scorpion.multitel.be> Le samedi 27 d?cembre 2008 ? 18:15 -0600, LiQun Li a ?crit : > Hi, > I try to set up Ekiga to connect freedigits.net. > after setting up, it shows: > Registration failed: Forbidden > on its status bar. > > what does it mean? > what should I do? That the password you provided is not valid. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From dsandras at seconix.com Sun Dec 28 18:00:50 2008 From: dsandras at seconix.com (Damien Sandras) Date: Sun, 28 Dec 2008 19:00:50 +0100 Subject: [Ekiga-list] could not register : behind a router In-Reply-To: References: <1229373582.13601.45.camel@scorpion.multitel.be> <1229414703.13601.53.camel@scorpion.multitel.be> <4949063A.6070809@gmail.com> <1229542762.4276.8.camel@scorpion.multitel.be> <1229784717.27064.2.camel@scorpion.multitel.be> Message-ID: <1230487250.4343.4.camel@scorpion.multitel.be> Is that 3.0 or 2.0 ? Le dimanche 28 d?cembre 2008 ? 17:21 +0300, Fedor vonBock a ?crit : > is it the network settings page on ekiga? there isn't one. > > > I've enabled my PC (ubuntu hardy) to use a static ip address. how is > the translation happening then? > > > On Sat, Dec 20, 2008 at 5:51 PM, Damien Sandras > wrote: > > 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:dsandras at ekiga.net > > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From dsandras at seconix.com Sun Dec 28 17:59:41 2008 From: dsandras at seconix.com (Damien Sandras) Date: Sun, 28 Dec 2008 18:59:41 +0100 Subject: [Ekiga-list] Compile Problem In-Reply-To: <49571AD4.1010703@astronomicalresearchaustralia.org> References: <49556360.000002.20513@kamasutra> <4955853F.4090407@astronomicalresearchaustralia.org> <1230373752.24875.14.camel@scorpion.multitel.be> <49562D88.6090909@astronomicalresearchaustralia.org> <1230409601.30628.0.camel@scorpion.multitel.be> <49571AD4.1010703@astronomicalresearchaustralia.org> Message-ID: <1230487181.4343.0.camel@scorpion.multitel.be> Hi, Le dimanche 28 d?cembre 2008 ? 16:21 +1000, Brian a ?crit : > Damien, > I have tried lots of options here( I have been working on this for two > days), however, I am really stuck now. > I think you are right it is probably due to me running a suse/kde > system. So I have given up for now( I am going to try and get some local > help). > In the meantime I have installed the 3.0.1-1.22 binary I found on rpmfind. > This works fine except that it cannot open the camera, see below. > The camera( a v4l2) works fine in 3 other applications. > Other messages say that PTLIB recogised that the camera was v4l2. > However, when I get to the part in the wizard to select the camera, it > does not give me any choices it just says (046d:08c1PTLIB/V4L). Can you provide a full log ? I fear the V4L2 plugin is not installed, but only the 'deprecated' V4L2 plugin... -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From dsandras at beip.be Sun Dec 28 18:08:59 2008 From: dsandras at beip.be (Damien Sandras) Date: Sun, 28 Dec 2008 19:08:59 +0100 Subject: [Ekiga-list] Problem connecting ekiga 3 to ekiga 2 In-Reply-To: <1230487678.4343.9.camel@scorpion.multitel.be> References: <7ca14f9d0812280656u3a7d2e86o215437721b8a9ec0@mail.gmail.com> <1230487678.4343.9.camel@scorpion.multitel.be> Message-ID: <1230487739.4343.11.camel@scorpion.multitel.be> Le dimanche 28 d?cembre 2008 ? 19:07 +0100, Damien Sandras a ?crit : > Le dimanche 28 d?cembre 2008 ? 15:56 +0100, Jiri Cerny a ?crit : > > Recently I upgraded from Ekiga 2 to Ekiga 3 (by upgrading from Fedora > > 9 to Fedora 10). Since then I have problem to call my sister which > > still uses Ekiga 2 (more precisely quite old Ekiga 2.0.1 on Fedora > > Core 5, which cannot be upgraded easily). The problem is that she can > > hear me but I cannot hear her. > > > > When I reboot back to Fedora 9 and use Ekiga 2.0.12 (I think) to call > > her, then everything works fine, so there is not obvious problem with > > her setup. If I call 500 at ekiga.net from Ekiga 3.0, then everything is > > also fine. > > > > I have got logs from one unsuccessful call, but I do not understand > > them very well. They are attached to this email. Can you see from > > them, where the problem is? Thank for your help. > > There is something weird : it asks to receive audio on port 5062, it > means that it is probably the same port on the router and on the desktop > PC. > > However, it happens in both log, but in the Ekiga 3 log, you receive no > audio. > > Can you check with tcpdump and / or wireshark if you actually receive > something on port 5062 ? (Or any other port specified in the line with "audio" appearing in the INVITE body). -- _ Damien Sandras (o- //\ Be IP s.a. - Don't be worried, Be IP! v_/_ W: www.beip.be T: +32 65 39 91 00 F: +32 65 39 91 01 From jmeili at gmx.ch Sun Dec 28 18:24:51 2008 From: jmeili at gmx.ch (Judith Meili) Date: Sun, 28 Dec 2008 19:24:51 +0100 Subject: [Ekiga-list] echo canceller Message-ID: <4957C473.9070109@gmx.ch> Hello I enjoy to make phone calls with Ekiga. But the receivers of my calls complain concerning the echo. Where is the echo canceller for Ekiga? Thanks. Br jm From palos at post.sk Sun Dec 28 19:36:37 2008 From: palos at post.sk (Palo S.) Date: 28 Dec 2008 20:36:37 +0100 (CET) Subject: [Ekiga-list] 473 Filtered destination Message-ID: <4957D545.000001.20416@kamasutra> > > > > > > > > > > Does TRUNK give the same problem ? > > > > TRUNK gives the same problem. Furthermore I reproduced > > the same problem on two other computers: one in the same > > LAN and one in completely different network environment. > > > > Are you talking about the REGISTER not being refreshed ? Yes (although it looks more like _any_ communication between the client and server suddenly stops, not just registering - have a look at the log I attached previously). This behaviour is the same and always reproducible in 3.0.1 and trunk and on all 4 computers at 3 different locations that I have tested so far. The time after which this happens differs but seems to be between 50-100 minutes. Palo __________ http://www.tahaj.sk - Stiahnite si najnovsie verzie vasich oblubenych programov From bnc at astronomicalresearchaustralia.org Mon Dec 29 01:52:44 2008 From: bnc at astronomicalresearchaustralia.org (Brian) Date: Mon, 29 Dec 2008 11:52:44 +1000 Subject: [Ekiga-list] Compile Problem In-Reply-To: <1230487181.4343.0.camel@scorpion.multitel.be> References: <49556360.000002.20513@kamasutra> <4955853F.4090407@astronomicalresearchaustralia.org> <1230373752.24875.14.camel@scorpion.multitel.be> <49562D88.6090909@astronomicalresearchaustralia.org> <1230409601.30628.0.camel@scorpion.multitel.be> <49571AD4.1010703@astronomicalresearchaustralia.org> <1230487181.4343.0.camel@scorpion.multitel.be> Message-ID: <49582D6C.1040901@astronomicalresearchaustralia.org> Damien, > > Can you provide a full log ? Do you mean from a ekiga -d 4? > > I fear the V4L2 plugin is not installed, but only the 'deprecated' V4L2 > > plugin... > > I agree, that is what it looks like and last time I got out of the same situation by installing the latest pwlib. I believe I have the latest installed, see below. Brian pwlib-plugins-v4l2 - V4L2 support for pwlib This plugin enables 'video for linux' (version 2) support (e.g. for USB cameras) for pwlib. The level of support is unspecified pwlib-plugins-v4l2-1.10.10-56.2 - V4L2 support for pwlib /usr/lib/pwlib/devices/videoinput /usr/lib/pwlib/devices/videoinput/v4l2_pwplugin.so 2 files total pwlib-plugins-v4l2 - V4L2 support for pwlib Alternate Version 1.10.10-56.2 Installed Version 1.10.10-120.55 Build Time: Wed Dec 10 12:02:58 2008 Wed Dec 3 20:36:20 2008 Install Time: Fri Dec 26 15:29:35 2008 Package Group: System/Libraries License: MOZILLA PUBLIC LICENSE (MPL/NPL) Installed Size: 105.0 K 83.0 K Download Size: 34.0 K 0 B Distribution: openSUSE 11.1 Vendor: openSUSE Build Service openSUSE Packager: http://bugs.opensuse.org Architecture: i586 i586 Build Host: URL: http://www.openh323.org/ http://www.openh323.org/ Media No.: 0 0 Authors: Equivalence Pty. Ltd. Equivalence Pty. Ltd. From zhangweiwu at realss.com Mon Dec 29 02:55:19 2008 From: zhangweiwu at realss.com (Zhang Weiwu) Date: Mon, 29 Dec 2008 10:55:19 +0800 Subject: [Ekiga-list] quick help appreciated: ekiga always report symmetric NAT even after port-forwarding enabled. Message-ID: <49583C17.20300@realss.com> 1. If I set my notebook as DMZ, ekiga report I have cone NAT and thus should work. But I cannot keep my notebook as DMZ for local network management reasons; 2. If I don't set my notebook as DMZ, ekiga always report I have symmetric NAT even if I enable port-forwarding strictly according to recommendation; 1. router (act as NAT firewall) setting is attached to this email. Note 192.168.1.101 is IP address of my notebook; 2. there is only 1 public IP address for this router; 3. router setting is tested using netcat (running 'nc -u -l -p 5062' on my notebook and run 'nc -u emerson.realss.com 5062' on a remote server, test UDP port forwarding works fine by typing hello world on remote server and see it comes out locally); Fast help highly appreciated because I am trying to start an online meeting. Other information: a) screenshot of ekiga is provided; b) netstat -l on notebook attached as following zhangweiwu at esmeralda:~$ netstat -ltu Aktive Internetverbindungen (Nur Server) Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 *:sunrpc *:* LISTEN tcp 0 0 *:x11 *:* LISTEN tcp 0 0 *:http *:* LISTEN tcp 0 0 *:ssh *:* LISTEN tcp 0 0 localhost:ipp *:* LISTEN tcp 0 0 192.168.1.:h323hostcall *:* LISTEN udp 0 0 192.168.1.255:5060 *:* udp 0 0 192.168.1.101:5060 *:* udp 0 0 *:bootpc *:* udp 0 0 *:bootpc *:* udp 0 0 *:5063 *:* udp 0 0 *:5064 *:* udp 0 0 *:5065 *:* udp 0 0 *:5066 *:* udp 0 0 *:sunrpc *:* udp 0 0 *:ipp *:* -- Real Softservice Huateng Tower, Unit 1788 Jia 302 3rd area of Jinsong, Chao Yang Tel: +86 (10) 8773 0650 ext 603 Mobile: 159 1111 7382 http://www.realss.com -------------- next part -------------- A non-text attachment was scrubbed... Name: router_setting.png Type: image/png Size: 6000 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ekiga_error_msg.png Type: image/png Size: 7012 bytes Desc: not available URL: From andre at bwh.harvard.edu Mon Dec 29 03:04:59 2008 From: andre at bwh.harvard.edu (Andre Robatino) Date: Sun, 28 Dec 2008 22:04:59 -0500 Subject: [Ekiga-list] quick help appreciated: ekiga always report symmetric NAT even after port-forwarding enabled. In-Reply-To: <49583C17.20300@realss.com> References: <49583C17.20300@realss.com> Message-ID: <49583E5B.50302@bwh.harvard.edu> If you don't need the video you could try using Twinkle instead of Ekiga. My father has a symmetric NAT router with the necessary port triggering (not port forwarding) enabled. Even though Twinkle gives a similar error message to Ekiga 3.0 on startup about not being able to work due to symmetric NAT, it works properly anyway. He previously used Ekiga 2.0 but something changed from version 2 to 3 to prevent it working for him even though the router configuration never changed. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3266 bytes Desc: S/MIME Cryptographic Signature URL: From fshock at hotmail.com Mon Dec 29 03:19:20 2008 From: fshock at hotmail.com (FS Inc.) Date: Mon, 29 Dec 2008 03:19:20 +0000 Subject: [Ekiga-list] quick help appreciated: ekiga always report symmetric NAT even after port-forwarding enabled. In-Reply-To: <49583C17.20300@realss.com> References: <49583C17.20300@realss.com> Message-ID: I am on a linksys router wrt54g that reports symentric NAT,What was recommended was to use port triggering as opposed to port forwarding. I am not too sure what the difference is, But basically i followed this link ...http://wiki.ekiga.org/index.php/Ekiga_behind_a_NAT_router (Symmetric NAT: Dynamic navigation of NAT routers section)> Date: Mon, 29 Dec 2008 10:55:19 +0800> From: zhangweiwu at realss.com> To: ekiga-list at gnome.org> Subject: [Ekiga-list] quick help appreciated: ekiga always report symmetric NAT even after port-forwarding enabled.> > 1. If I set my notebook as DMZ, ekiga report I have cone NAT and> thus should work. But I cannot keep my notebook as DMZ for local> network management reasons;> 2. If I don't set my notebook as DMZ, ekiga always report I have> symmetric NAT even if I enable port-forwarding strictly according> to recommendation;> 1. router (act as NAT firewall) setting is attached to this> email. Note 192.168.1.101 is IP address of my notebook;> 2. there is only 1 public IP address for this router;> 3. router setting is tested using netcat (running 'nc -u -l -p> 5062' on my notebook and run 'nc -u emerson.realss.com 5062'> on a remote server, test UDP port forwarding works fine by> typing hello world on remote server and see it comes out> locally);> > > Fast help highly appreciated because I am trying to start an online meeting.> > Other information: a) screenshot of ekiga is provided; b) netstat -l on> notebook attached as following> > zhangweiwu at esmeralda:~$ netstat -ltu> Aktive Internetverbindungen (Nur Server)> Proto Recv-Q Send-Q Local Address Foreign Address> State> tcp 0 0 *:sunrpc *:*> LISTEN> tcp 0 0 *:x11 *:*> LISTEN> tcp 0 0 *:http *:*> LISTEN> tcp 0 0 *:ssh *:*> LISTEN> tcp 0 0 localhost:ipp *:*> LISTEN> tcp 0 0 192.168.1.:h323hostcall *:*> LISTEN> udp 0 0 192.168.1.255:5060 *:*> > udp 0 0 192.168.1.101:5060 *:*> > udp 0 0 *:bootpc *:*> > udp 0 0 *:bootpc *:*> > udp 0 0 *:5063 *:*> > udp 0 0 *:5064 *:*> > udp 0 0 *:5065 *:*> > udp 0 0 *:5066 *:*> > udp 0 0 *:sunrpc *:*> > udp 0 0 *:ipp *:*> > > -- > Real Softservice> > Huateng Tower, Unit 1788> Jia 302 3rd area of Jinsong, Chao Yang> > Tel: +86 (10) 8773 0650 ext 603> Mobile: 159 1111 7382> http://www.realss.com> > _________________________________________________________________ Show them the way! Add maps and directions to your party invites. http://www.microsoft.com/windows/windowslive/events.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From andre at bwh.harvard.edu Mon Dec 29 03:26:26 2008 From: andre at bwh.harvard.edu (Andre Robatino) Date: Sun, 28 Dec 2008 22:26:26 -0500 Subject: [Ekiga-list] quick help appreciated: ekiga always report symmetric NAT even after port-forwarding enabled. In-Reply-To: References: <49583C17.20300@realss.com> Message-ID: <49584362.7060805@bwh.harvard.edu> FS Inc. wrote: > I am on a linksys router wrt54g that reports symentric NAT, > > What was recommended was to use port triggering as opposed to port > forwarding. I am not too sure what the difference is, But basically i > followed this link ... > > http://wiki.ekiga.org/index.php/Ekiga_behind_a_NAT_router (Symmetric > NAT: Dynamic navigation of NAT routers section) This is exactly the way my father has his Motorola 2210-02-1006 router configured. But it no longer works for him with Ekiga 3. Which version are you using? -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3266 bytes Desc: S/MIME Cryptographic Signature URL: From fshock at hotmail.com Mon Dec 29 03:53:25 2008 From: fshock at hotmail.com (FS Inc.) Date: Mon, 29 Dec 2008 03:53:25 +0000 Subject: [Ekiga-list] quick help appreciated: ekiga always report symmetric NAT even after port-forwarding enabled. In-Reply-To: <49584362.7060805@bwh.harvard.edu> References: <49583C17.20300@realss.com> <49584362.7060805@bwh.harvard.edu> Message-ID: version 2. I'm not having a problem that works for me. was posting the link for the other poster to see if it helped him.> Date: Sun, 28 Dec 2008 22:26:26 -0500> From: andre at bwh.harvard.edu> To: ekiga-list at gnome.org> Subject: Re: [Ekiga-list] quick help appreciated: ekiga always report symmetric NAT even after port-forwarding enabled.> > FS Inc. wrote:> > I am on a linksys router wrt54g that reports symentric NAT,> > > > What was recommended was to use port triggering as opposed to port > > forwarding. I am not too sure what the difference is, But basically i > > followed this link ...> > > > http://wiki.ekiga.org/index.php/Ekiga_behind_a_NAT_router (Symmetric > > NAT: Dynamic navigation of NAT routers section)> > This is exactly the way my father has his Motorola 2210-02-1006 router > configured. But it no longer works for him with Ekiga 3. Which version > are you using?> _________________________________________________________________ Show them the way! Add maps and directions to your party invites. http://www.microsoft.com/windows/windowslive/events.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhangweiwu at realss.com Mon Dec 29 03:57:29 2008 From: zhangweiwu at realss.com (Zhang Weiwu) Date: Mon, 29 Dec 2008 11:57:29 +0800 Subject: [Ekiga-list] quick help appreciated: ekiga always report symmetric NAT even after port-forwarding enabled. In-Reply-To: References: <49583C17.20300@realss.com> Message-ID: <49584AA9.9030301@realss.com> FS Inc. wrote: > I am on a linksys router wrt54g that reports symentric NAT, > > What was recommended was to use port triggering as opposed to port > forwarding. I am not too sure what the difference is, But basically > i followed this link ... > > http://wiki.ekiga.org/index.php/Ekiga_behind_a_NAT_router (Symmetric > NAT: Dynamic navigation of NAT routers section) Hi. Thank you very much. I am just back from the meeting. Following the link you gave me, the "trigger" section, it works instantly, a lot thanks! I am using version 2.0.11 From dsandras at seconix.com Mon Dec 29 08:33:34 2008 From: dsandras at seconix.com (Damien Sandras) Date: Mon, 29 Dec 2008 09:33:34 +0100 Subject: [Ekiga-list] Compile Problem In-Reply-To: <49582D6C.1040901@astronomicalresearchaustralia.org> References: <49556360.000002.20513@kamasutra> <4955853F.4090407@astronomicalresearchaustralia.org> <1230373752.24875.14.camel@scorpion.multitel.be> <49562D88.6090909@astronomicalresearchaustralia.org> <1230409601.30628.0.camel@scorpion.multitel.be> <49571AD4.1010703@astronomicalresearchaustralia.org> <1230487181.4343.0.camel@scorpion.multitel.be> <49582D6C.1040901@astronomicalresearchaustralia.org> Message-ID: <1230539614.4293.2.camel@scorpion.multitel.be> Le lundi 29 d?cembre 2008 ? 11:52 +1000, Brian a ?crit : > Damien, > > > Can you provide a full log ? > Do you mean from a ekiga -d 4? > Yes -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From dsandras at seconix.com Mon Dec 29 08:57:23 2008 From: dsandras at seconix.com (Damien Sandras) Date: Mon, 29 Dec 2008 09:57:23 +0100 Subject: [Ekiga-list] 473 Filtered destination In-Reply-To: <4957D545.000001.20416@kamasutra> References: <4957D545.000001.20416@kamasutra> Message-ID: <1230541043.4293.13.camel@scorpion.multitel.be> Le dimanche 28 d?cembre 2008 ? 20:36 +0100, Palo S. a ?crit : > > > > > > > > > > > > Does TRUNK give the same problem ? > > > > > > TRUNK gives the same problem. Furthermore I reproduced > > > the same problem on two other computers: one in the same > > > LAN and one in completely different network environment. > > > > > > > Are you talking about the REGISTER not being refreshed ? > > Yes (although it looks more like _any_ communication > between the client and server suddenly stops, not just > registering - have a look at the log I attached previously). > I still see SUBSCRIBE and NOTIFY and responses being exchanged. Only the REGISTER seems to be blocked or am I missing something ? -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From Eugen.Dedu at pu-pm.univ-fcomte.fr Mon Dec 29 10:32:34 2008 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Mon, 29 Dec 2008 11:32:34 +0100 Subject: [Ekiga-list] Compile Problem In-Reply-To: <49582D6C.1040901@astronomicalresearchaustralia.org> References: <49556360.000002.20513@kamasutra> <4955853F.4090407@astronomicalresearchaustralia.org> <1230373752.24875.14.camel@scorpion.multitel.be> <49562D88.6090909@astronomicalresearchaustralia.org> <1230409601.30628.0.camel@scorpion.multitel.be> <49571AD4.1010703@astronomicalresearchaustralia.org> <1230487181.4343.0.camel@scorpion.multitel.be> <49582D6C.1040901@astronomicalresearchaustralia.org> Message-ID: <4958A742.9060808@pu-pm.univ-fcomte.fr> Brian wrote: > Damien, >>> Can you provide a full log ? > Do you mean from a ekiga -d 4? > >>> I fear the V4L2 plugin is not installed, but only the 'deprecated' V4L2 >>> plugin... >>> > > I agree, that is what it looks like and last time I got out of the same > situation by installing the latest pwlib. > > I believe I have the latest installed, see below. > > Brian > > > pwlib-plugins-v4l2 - V4L2 support for pwlib > > This plugin enables 'video for linux' (version 2) support (e.g. for USB > cameras) for pwlib. > The level of support is unspecified > > > pwlib-plugins-v4l2-1.10.10-56.2 - V4L2 support for pwlib This is the old plugin. ekiga 3.0 compiles only with the latest versions of ptlib (previously caled pwlib) and opal: ptlib 2.4.2 (you have here 1.10.10) and opal 3.4.2. -- Eugen From bnc at astronomicalresearchaustralia.org Mon Dec 29 11:24:49 2008 From: bnc at astronomicalresearchaustralia.org (Brian) Date: Mon, 29 Dec 2008 21:24:49 +1000 Subject: [Ekiga-list] Compile Problem In-Reply-To: <4958A742.9060808@pu-pm.univ-fcomte.fr> References: <49556360.000002.20513@kamasutra> <4955853F.4090407@astronomicalresearchaustralia.org> <1230373752.24875.14.camel@scorpion.multitel.be> <49562D88.6090909@astronomicalresearchaustralia.org> <1230409601.30628.0.camel@scorpion.multitel.be> <49571AD4.1010703@astronomicalresearchaustralia.org> <1230487181.4343.0.camel@scorpion.multitel.be> <49582D6C.1040901@astronomicalresearchaustralia.org> <4958A742.9060808@pu-pm.univ-fcomte.fr> Message-ID: <4958B381.4000708@astronomicalresearchaustralia.org> Eugen, >> >> >> pwlib-plugins-v4l2-1.10.10-56.2 - V4L2 support for pwlib > > This is the old plugin. > Yes I agree, unfortunately emails do not convey levels of frustration:) > ekiga 3.0 compiles only with the latest versions of ptlib (previously > caled pwlib) and opal: ptlib 2.4.2 (you have here 1.10.10) and opal 3.4.2. > I have 3.0.1 plus Opal 3.4.3 plus ptlib 2.4.2 here each in a separate directory. I compiled opal and ptlib with no apparent problem. However, try as I might I could not get 3.0.1 to compile. Is there some subtle thing I am missing like putting opal and ptlib in some directory? Telling ekiga where to find the other two? Also not I am running a kde system, so I think it even money that I am missing some gnome stuff. After about two days I have up and went back to the supplied suse version, with as you correctly say pwlib problems. With this the echo test to 500 at ekiga.net works but no video etc. In a nutshell I know I really need to get 3.0.1 going. The frustrating thing is that a friend dropped it in on a deb system and was making calls within 30mins:) Thanks, Brian From jmeili at gmx.ch Mon Dec 29 10:35:48 2008 From: jmeili at gmx.ch (Judith Meili) Date: Mon, 29 Dec 2008 11:35:48 +0100 Subject: [Ekiga-list] [Fwd: echo canceller] Message-ID: <4958A804.3020501@gmx.ch> Who can answer? Thanks. -------- Original-Nachricht -------- Betreff: [Ekiga-list] echo canceller Datum: Sun, 28 Dec 2008 19:24:51 +0100 Von: Judith Meili Antwort an: Ekiga mailing list An: ekiga-list at gnome.org Hello I enjoy to make phone calls with Ekiga. But the receivers of my calls complain concerning the echo. Where is the echo canceller for Ekiga? Thanks. Br jm _______________________________________________ ekiga-list mailing list ekiga-list at gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list -------------- next part -------------- An HTML attachment was scrubbed... URL: From sevmek at free.fr Mon Dec 29 12:20:01 2008 From: sevmek at free.fr (yannick) Date: Mon, 29 Dec 2008 13:20:01 +0100 Subject: [Ekiga-list] [Fwd: echo canceller] In-Reply-To: <4958A804.3020501@gmx.ch> References: <4958A804.3020501@gmx.ch> Message-ID: <1230553201.32518.0.camel@achille> Le lundi 29 d?cembre 2008 ? 11:35 +0100, Judith Meili a ?crit : > Who can answer? Thanks. > Hello, Here it is: http://wiki.ekiga.org/index.php/Image:Capture-Ekiga_Preferences.png But it does not work in all cases... > -------- Original-Nachricht -------- > Betreff: > [Ekiga-list] echo canceller > Datum: > Sun, 28 Dec 2008 19:24:51 +0100 > Von: > Judith Meili > Antwort an: > Ekiga mailing list > > An: > ekiga-list at gnome.org > > > Hello > > I enjoy to make phone calls with Ekiga. But the receivers of my calls > complain concerning the echo. Where is the echo canceller for Ekiga? > > Thanks. > > Br > jm > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list -- Me joindre en t?l?phonie IP / vid?oconf?rence ? sip:yannick at ekiga.net Logiciel de VoIP Ekiga : http://www.ekiga.org http://wiki.ekiga.org/index.php/Which_programs_work_with_Ekiga_%3F From palos at post.sk Mon Dec 29 12:36:25 2008 From: palos at post.sk (Palo S.) Date: 29 Dec 2008 13:36:25 +0100 (CET) Subject: [Ekiga-list] 473 Filtered destination Message-ID: <4958C449.000001.05396@kamasutra> > > I still see SUBSCRIBE and NOTIFY and responses being exchanged. Only the > REGISTER seems to be blocked or am I missing something ? SUBSCRIBE and NOTIFY are only exchanged for a few minutes: 21:17:48 last REGISTER (expires 600) 21:22:46 last SUBSCRIBE (expires 300) and then absolutely nothing till 23:18 when I quit Ekiga (well, I had to kill it) I am really wondering about my 100% reproducibility on other machines and in other networks. Why does nobody else complain about this then? Could it be distribution specific from some reason? There is Fedora 8, 9 or 10 running on all these machines (and the problem is also reproducible with Ekiga 3 from Fedora 10 repositories) At the moment I workaround it by a script that kills Ekiga if the log file has not been modified for some time... Palo __________ http://cestovanie.sme.sk/ - Cel? svet na va?om monitore From jmeili at gmx.ch Mon Dec 29 11:38:10 2008 From: jmeili at gmx.ch (Judith Meili) Date: Mon, 29 Dec 2008 12:38:10 +0100 Subject: [Ekiga-list] [Fwd: echo canceller] In-Reply-To: <1230553201.32518.0.camel@achille> References: <4958A804.3020501@gmx.ch> <1230553201.32518.0.camel@achille> Message-ID: <4958B6A2.7090501@gmx.ch> Thanks. You do not even have a hook at "enable echo cancelation". I have a hook there and a hook where ever you show a hook and the people are still complaining. Can't Ekiga improve that? yannick schrieb: > Le lundi 29 d?cembre 2008 ? 11:35 +0100, Judith Meili a ?crit : > >> Who can answer? Thanks. >> >> > > Hello, > > Here it is: > http://wiki.ekiga.org/index.php/Image:Capture-Ekiga_Preferences.png > > But it does not work in all cases... > > >> -------- Original-Nachricht -------- >> Betreff: >> [Ekiga-list] echo canceller >> Datum: >> Sun, 28 Dec 2008 19:24:51 +0100 >> Von: >> Judith Meili >> Antwort an: >> Ekiga mailing list >> >> An: >> ekiga-list at gnome.org >> >> >> Hello >> >> I enjoy to make phone calls with Ekiga. But the receivers of my calls >> complain concerning the echo. Where is the echo canceller for Ekiga? >> >> Thanks. >> >> Br >> jm >> _______________________________________________ >> ekiga-list mailing list >> ekiga-list at gnome.org >> http://mail.gnome.org/mailman/listinfo/ekiga-list >> >> _______________________________________________ >> ekiga-list mailing list >> ekiga-list at gnome.org >> http://mail.gnome.org/mailman/listinfo/ekiga-list >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From dsandras at seconix.com Mon Dec 29 12:53:15 2008 From: dsandras at seconix.com (Damien Sandras) Date: Mon, 29 Dec 2008 13:53:15 +0100 Subject: [Ekiga-list] 473 Filtered destination In-Reply-To: <4958C449.000001.05396@kamasutra> References: <4958C449.000001.05396@kamasutra> Message-ID: <1230555195.4293.33.camel@scorpion.multitel.be> Le lundi 29 d?cembre 2008 ? 13:36 +0100, Palo S. a ?crit : > > > > I still see SUBSCRIBE and NOTIFY and responses being exchanged. Only the > > REGISTER seems to be blocked or am I missing something ? > > SUBSCRIBE and NOTIFY are only exchanged for a few minutes: > 21:17:48 last REGISTER (expires 600) > 21:22:46 last SUBSCRIBE (expires 300) > and then absolutely nothing till 23:18 when I quit > Ekiga (well, I had to kill it) > > I am really wondering about my 100% reproducibility > on other machines and in other networks. Why does > nobody else complain about this then? Could it be > distribution specific from some reason? There is > Fedora 8, 9 or 10 running on all these machines > (and the problem is also reproducible with Ekiga 3 > from Fedora 10 repositories) > > At the moment I workaround it by a script that kills > Ekiga if the log file has not been modified for some > time... > You are right... -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From f.vonbock at gmail.com Mon Dec 29 17:32:26 2008 From: f.vonbock at gmail.com (Fedor vonBock) Date: Mon, 29 Dec 2008 20:32:26 +0300 Subject: [Ekiga-list] could not register : behind a router In-Reply-To: <1230487250.4343.4.camel@scorpion.multitel.be> References: <1229373582.13601.45.camel@scorpion.multitel.be> <1229414703.13601.53.camel@scorpion.multitel.be> <4949063A.6070809@gmail.com> <1229542762.4276.8.camel@scorpion.multitel.be> <1229784717.27064.2.camel@scorpion.multitel.be> <1230487250.4343.4.camel@scorpion.multitel.be> Message-ID: 3.0 On Sun, Dec 28, 2008 at 9:00 PM, Damien Sandras wrote: > Is that 3.0 or 2.0 ? > > Le dimanche 28 d?cembre 2008 ? 17:21 +0300, Fedor vonBock a ?crit : > > is it the network settings page on ekiga? there isn't one. > > > > > > I've enabled my PC (ubuntu hardy) to use a static ip address. how is > > the translation happening then? > > > > > > On Sat, Dec 20, 2008 at 5:51 PM, Damien Sandras > > wrote: > > > > 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:dsandras at ekiga.net > > > > > > _______________________________________________ > > ekiga-list mailing list > > ekiga-list at gnome.org > > http://mail.gnome.org/mailman/listinfo/ekiga-list > > > > > > _______________________________________________ > > ekiga-list mailing list > > ekiga-list at gnome.org > > http://mail.gnome.org/mailman/listinfo/ekiga-list > -- > _ Damien Sandras > (o- > //\ Ekiga Softphone : http://www.ekiga.org/ > v_/_ Be IP : http://www.beip.be/ > FOSDEM : http://www.fosdem.org/ > SIP Phone : sip:dsandras at ekiga.net > > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dsandras at seconix.com Mon Dec 29 18:02:49 2008 From: dsandras at seconix.com (Damien Sandras) Date: Mon, 29 Dec 2008 19:02:49 +0100 Subject: [Ekiga-list] could not register : behind a router In-Reply-To: References: <1229373582.13601.45.camel@scorpion.multitel.be> <1229414703.13601.53.camel@scorpion.multitel.be> <4949063A.6070809@gmail.com> <1229542762.4276.8.camel@scorpion.multitel.be> <1229784717.27064.2.camel@scorpion.multitel.be> <1230487250.4343.4.camel@scorpion.multitel.be> Message-ID: <1230573769.4293.66.camel@scorpion.multitel.be> OK, then there is no network translation... Le lundi 29 d?cembre 2008 ? 20:32 +0300, Fedor vonBock a ?crit : > 3.0 > > > On Sun, Dec 28, 2008 at 9:00 PM, Damien Sandras > wrote: > Is that 3.0 or 2.0 ? > > Le dimanche 28 d?cembre 2008 ? 17:21 +0300, Fedor vonBock a > ?crit : > > > is it the network settings page on ekiga? there isn't one. > > > > > > I've enabled my PC (ubuntu hardy) to use a static ip > address. how is > > the translation happening then? > > > > > > On Sat, Dec 20, 2008 at 5:51 PM, Damien Sandras > > > wrote: > > > > 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:dsandras at ekiga.net > > > > > > _______________________________________________ > > ekiga-list mailing list > > ekiga-list at gnome.org > > http://mail.gnome.org/mailman/listinfo/ekiga-list > > > > > > _______________________________________________ > > ekiga-list mailing list > > ekiga-list at gnome.org > > http://mail.gnome.org/mailman/listinfo/ekiga-list > > -- > > _ Damien Sandras > (o- > //\ Ekiga Softphone : http://www.ekiga.org/ > v_/_ Be IP : http://www.beip.be/ > FOSDEM : http://www.fosdem.org/ > SIP Phone : sip:dsandras at ekiga.net > > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From jmeili at gmx.ch Mon Dec 29 19:49:40 2008 From: jmeili at gmx.ch (Judith Meili) Date: Mon, 29 Dec 2008 20:49:40 +0100 Subject: [Ekiga-list] [Fwd: Re: [Fwd: echo canceller]] Message-ID: <495929D4.7090404@gmx.ch> Damien Sandras? Do you want to answer? -------- Original-Nachricht -------- Betreff: Re: [Ekiga-list] [Fwd: echo canceller] Datum: Mon, 29 Dec 2008 12:38:10 +0100 Von: Judith Meili Antwort an: Ekiga mailing list An: Ekiga mailing list Referenzen: <4958A804.3020501 at gmx.ch> <1230553201.32518.0.camel at achille> Thanks. You do not even have a hook at "enable echo cancelation". I have a hook there and a hook where ever you show a hook and the people are still complaining. Can't Ekiga improve that? yannick schrieb: > Le lundi 29 d?cembre 2008 ? 11:35 +0100, Judith Meili a ?crit : > >> Who can answer? Thanks. >> >> > > Hello, > > Here it is: > http://wiki.ekiga.org/index.php/Image:Capture-Ekiga_Preferences.png > > But it does not work in all cases... > > >> -------- Original-Nachricht -------- >> Betreff: >> [Ekiga-list] echo canceller >> Datum: >> Sun, 28 Dec 2008 19:24:51 +0100 >> Von: >> Judith Meili >> Antwort an: >> Ekiga mailing list >> >> An: >> ekiga-list at gnome.org >> >> >> Hello >> >> I enjoy to make phone calls with Ekiga. But the receivers of my calls >> complain concerning the echo. Where is the echo canceller for Ekiga? >> >> Thanks. >> >> Br >> jm >> _______________________________________________ >> ekiga-list mailing list >> ekiga-list at gnome.org >> http://mail.gnome.org/mailman/listinfo/ekiga-list >> >> _______________________________________________ >> ekiga-list mailing list >> ekiga-list at gnome.org >> http://mail.gnome.org/mailman/listinfo/ekiga-list >> -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: Nachrichtenteil als Anhang URL: From jmeili at gmx.ch Tue Dec 30 07:29:19 2008 From: jmeili at gmx.ch (Judith Meili) Date: Tue, 30 Dec 2008 08:29:19 +0100 Subject: [Ekiga-list] Audio-Problems Message-ID: <4959CDCF.7060906@gmx.ch> Hello Why do I get this message? "Audiokanal zum Audioempfang konnte nicht ge?ffnet werden Beim Versuch, Audio f?r den Audio-Empfang ?ber die Soundkarte auszugeben, ist ein Fehler aufgetreten. Bitte ?berpr?fen Sie, dass die Soundkarte nicht anderweitig benutzt wird und dass der Treiber Voll-Duplex unterst?tzt. Der Audioempfang wurde deaktiviert." Br jm From dsandras at seconix.com Tue Dec 30 08:30:41 2008 From: dsandras at seconix.com (Damien Sandras) Date: Tue, 30 Dec 2008 09:30:41 +0100 Subject: [Ekiga-list] Audio-Problems In-Reply-To: <4959CDCF.7060906@gmx.ch> References: <4959CDCF.7060906@gmx.ch> Message-ID: <1230625841.5078.4.camel@scorpion.multitel.be> Hello, Le mardi 30 d?cembre 2008 ? 08:29 +0100, Judith Meili a ?crit : > Hello > > Why do I get this message? > > "Audiokanal zum Audioempfang konnte nicht ge?ffnet werden > > Beim Versuch, Audio f?r den Audio-Empfang ?ber die Soundkarte > auszugeben, ist ein Fehler aufgetreten. Bitte ?berpr?fen Sie, dass die > Soundkarte nicht anderweitig benutzt wird und dass der Treiber > Voll-Duplex unterst?tzt. > Der Audioempfang wurde deaktiviert." > La carte son est d?j? occup?e par un autre programme ? -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From dsandras at seconix.com Tue Dec 30 08:31:28 2008 From: dsandras at seconix.com (Damien Sandras) Date: Tue, 30 Dec 2008 09:31:28 +0100 Subject: [Ekiga-list] [Fwd: Re: [Fwd: echo canceller]] In-Reply-To: <495929D4.7090404@gmx.ch> References: <495929D4.7090404@gmx.ch> Message-ID: <1230625888.5078.6.camel@scorpion.multitel.be> Le lundi 29 d?cembre 2008 ? 20:49 +0100, Judith Meili a ?crit : > Damien Sandras? Do you want to answer? > > -------- Original-Nachricht -------- > Betreff: > Re: [Ekiga-list] [Fwd: echo > canceller] > Datum: > Mon, 29 Dec 2008 12:38:10 +0100 > Von: > Judith Meili > Antwort an: > Ekiga mailing list > > An: > Ekiga mailing list > > Referenzen: > <4958A804.3020501 at gmx.ch> > <1230553201.32518.0.camel at achille> > > > Thanks. You do not even have a hook at "enable echo cancelation". I > have a hook there and a hook where ever you show a hook and the people > are still complaining. Can't Ekiga improve that? > Improve echo cancellation ? We use the best algorithm currently available. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From jmeili at gmx.ch Tue Dec 30 07:34:13 2008 From: jmeili at gmx.ch (Judith Meili) Date: Tue, 30 Dec 2008 08:34:13 +0100 Subject: [Ekiga-list] [Fwd: Re: [Fwd: echo canceller]] In-Reply-To: <1230625888.5078.6.camel@scorpion.multitel.be> References: <495929D4.7090404@gmx.ch> <1230625888.5078.6.camel@scorpion.multitel.be> Message-ID: <4959CEF5.4060800@gmx.ch> Thanks. So maybe the microphone is too close to the speaker? Everybody complains because of echo. Damien Sandras schrieb: > Le lundi 29 d?cembre 2008 ? 20:49 +0100, Judith Meili a ?crit : > >> Damien Sandras? Do you want to answer? >> >> -------- Original-Nachricht -------- >> Betreff: >> Re: [Ekiga-list] [Fwd: echo >> canceller] >> Datum: >> Mon, 29 Dec 2008 12:38:10 +0100 >> Von: >> Judith Meili >> Antwort an: >> Ekiga mailing list >> >> An: >> Ekiga mailing list >> >> Referenzen: >> <4958A804.3020501 at gmx.ch> >> <1230553201.32518.0.camel at achille> >> >> >> Thanks. You do not even have a hook at "enable echo cancelation". I >> have a hook there and a hook where ever you show a hook and the people >> are still complaining. Can't Ekiga improve that? >> >> > > Improve echo cancellation ? > We use the best algorithm currently available. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jmeili at gmx.ch Tue Dec 30 07:34:57 2008 From: jmeili at gmx.ch (Judith Meili) Date: Tue, 30 Dec 2008 08:34:57 +0100 Subject: [Ekiga-list] Audio-Problems In-Reply-To: <1230625841.5078.4.camel@scorpion.multitel.be> References: <4959CDCF.7060906@gmx.ch> <1230625841.5078.4.camel@scorpion.multitel.be> Message-ID: <4959CF21.2050302@gmx.ch> Mais par quel program? J'ai aucun program ouvert sauf skype. Damien Sandras schrieb: > Hello, > > Le mardi 30 d?cembre 2008 ? 08:29 +0100, Judith Meili a ?crit : > >> Hello >> >> Why do I get this message? >> >> "Audiokanal zum Audioempfang konnte nicht ge?ffnet werden >> >> Beim Versuch, Audio f?r den Audio-Empfang ?ber die Soundkarte >> auszugeben, ist ein Fehler aufgetreten. Bitte ?berpr?fen Sie, dass die >> Soundkarte nicht anderweitig benutzt wird und dass der Treiber >> Voll-Duplex unterst?tzt. >> Der Audioempfang wurde deaktiviert." >> >> > > La carte son est d?j? occup?e par un autre programme ? > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dsandras at seconix.com Tue Dec 30 09:35:12 2008 From: dsandras at seconix.com (Damien Sandras) Date: Tue, 30 Dec 2008 10:35:12 +0100 Subject: [Ekiga-list] [Fwd: Re: [Fwd: echo canceller]] In-Reply-To: <4959CEF5.4060800@gmx.ch> References: <495929D4.7090404@gmx.ch> <1230625888.5078.6.camel@scorpion.multitel.be> <4959CEF5.4060800@gmx.ch> Message-ID: <1230629712.5078.10.camel@scorpion.multitel.be> Le mardi 30 d?cembre 2008 ? 08:34 +0100, Judith Meili a ?crit : > Thanks. So maybe the microphone is too close to the speaker? Everybody > complains because of echo. > Are the speakers and microphones attached to the same soundcard or do you use speakers + USB mic or similar ? -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From dsandras at seconix.com Tue Dec 30 09:35:28 2008 From: dsandras at seconix.com (Damien Sandras) Date: Tue, 30 Dec 2008 10:35:28 +0100 Subject: [Ekiga-list] Audio-Problems In-Reply-To: <4959CF21.2050302@gmx.ch> References: <4959CDCF.7060906@gmx.ch> <1230625841.5078.4.camel@scorpion.multitel.be> <4959CF21.2050302@gmx.ch> Message-ID: <1230629728.5078.12.camel@scorpion.multitel.be> It's perhaps skype in that case. Le mardi 30 d?cembre 2008 ? 08:34 +0100, Judith Meili a ?crit : > Mais par quel program? J'ai aucun program ouvert sauf skype. > > Damien Sandras schrieb: > > Hello, > > > > Le mardi 30 d?cembre 2008 ? 08:29 +0100, Judith Meili a ?crit : > > > > > Hello > > > > > > Why do I get this message? > > > > > > "Audiokanal zum Audioempfang konnte nicht ge?ffnet werden > > > > > > Beim Versuch, Audio f?r den Audio-Empfang ?ber die Soundkarte > > > auszugeben, ist ein Fehler aufgetreten. Bitte ?berpr?fen Sie, dass die > > > Soundkarte nicht anderweitig benutzt wird und dass der Treiber > > > Voll-Duplex unterst?tzt. > > > Der Audioempfang wurde deaktiviert." > > > > > > > > > > La carte son est d?j? occup?e par un autre programme ? > > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From bnc at astronomicalresearchaustralia.org Tue Dec 30 10:46:49 2008 From: bnc at astronomicalresearchaustralia.org (Brian) Date: Tue, 30 Dec 2008 20:46:49 +1000 Subject: [Ekiga-list] Compile Problem In-Reply-To: <4958A742.9060808@pu-pm.univ-fcomte.fr> References: <49556360.000002.20513@kamasutra> <4955853F.4090407@astronomicalresearchaustralia.org> <1230373752.24875.14.camel@scorpion.multitel.be> <49562D88.6090909@astronomicalresearchaustralia.org> <1230409601.30628.0.camel@scorpion.multitel.be> <49571AD4.1010703@astronomicalresearchaustralia.org> <1230487181.4343.0.camel@scorpion.multitel.be> <49582D6C.1040901@astronomicalresearchaustralia.org> <4958A742.9060808@pu-pm.univ-fcomte.fr> Message-ID: <4959FC19.2070404@astronomicalresearchaustralia.org> Eugen, Thanks this put me on the right track. I can confirm that suse 11.1 is the problem. In ekiga-3.0.1/lib/engine/ it still uses *.la files all these have been removed in 11.1, in addition there is practically nothing in /opt/gnome/lib. Most of those files have been moved to /usr/lib. There were about 6 other files that were deleted altogether. What a mess! Anyway I got over all of them, and engine compiled ok. Now I get to /usr/lib/gcc/i586-suse-linux/4.3/../../../../i586-suse-linux/bin/ld: cannot find -lresmgr collect2: ld returned 1 exit status make[3]: *** [ekiga] Error 1 make[3]: Leaving directory `/Documents/SOURCE/SUSE11/ekiga-3.0.1/src' make[2]: *** [all] Error 2 make[2]: Leaving directory `/Documents/SOURCE/SUSE11/ekiga-3.0.1/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/Documents/SOURCE/SUSE11/ekiga-3.0.1' make: *** [all] Error 2 Only to discover that suse dropped support for resmgr after 10.3. It nolonger exists in 11.1. Suse now appears to use hal-resmgr. Once I figured out what libs were required where, I coped, but I do not understand how to proceed with this one. Is it possible to remove the requirement to load resmgr? Thanks, Brian Eugen Dedu wrote: > Brian wrote: >> Damien, >>>> Can you provide a full log ? >> Do you mean from a ekiga -d 4? >> >>>> I fear the V4L2 plugin is not installed, but only the 'deprecated' V4L2 >>>> plugin... >>>> >> >> I agree, that is what it looks like and last time I got out of the same >> situation by installing the latest pwlib. >> >> I believe I have the latest installed, see below. >> >> Brian >> >> >> pwlib-plugins-v4l2 - V4L2 support for pwlib >> >> This plugin enables 'video for linux' (version 2) support (e.g. for USB >> cameras) for pwlib. >> The level of support is unspecified >> >> >> pwlib-plugins-v4l2-1.10.10-56.2 - V4L2 support for pwlib > > This is the old plugin. > > ekiga 3.0 compiles only with the latest versions of ptlib (previously > caled pwlib) and opal: ptlib 2.4.2 (you have here 1.10.10) and opal 3.4.2. > From palos at post.sk Tue Dec 30 11:00:49 2008 From: palos at post.sk (Palo S.) Date: 30 Dec 2008 12:00:49 +0100 (CET) Subject: [Ekiga-list] 473 Filtered destination Message-ID: <4959FF61.000001.20636@kamasutra> I have reproduced the same problem on yet another computer running Ubuntu with Ekiga 3.0 packaged by Yannick. So my suspicion on distribution specificity is wrong. I am even more wondering why nobody else complains about this... weird. __________ Mobiln? telef?ny v slovenskej premi?re a najaktu?lnej?ie inform?cie - http://mobil.sme.sk/ From dsandras at seconix.com Tue Dec 30 10:55:55 2008 From: dsandras at seconix.com (Damien Sandras) Date: Tue, 30 Dec 2008 11:55:55 +0100 Subject: [Ekiga-list] 473 Filtered destination In-Reply-To: <4959FF61.000001.20636@kamasutra> References: <4959FF61.000001.20636@kamasutra> Message-ID: <1230634555.5078.16.camel@scorpion.multitel.be> Le mardi 30 d?cembre 2008 ? 12:00 +0100, Palo S. a ?crit : > I have reproduced the same problem on yet another computer > running Ubuntu with Ekiga 3.0 packaged by Yannick. So my > suspicion on distribution specificity is wrong. I am even > more wondering why nobody else complains about this... > weird. Can you try to remove from your contact list all things related to ekiga.net : 500 at ekiga.net, 501 at ekiga.net and so on ? You can keep your normal contacts. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From bnc at astronomicalresearchaustralia.org Tue Dec 30 11:03:53 2008 From: bnc at astronomicalresearchaustralia.org (Brian) Date: Tue, 30 Dec 2008 21:03:53 +1000 Subject: [Ekiga-list] Compile Problem In-Reply-To: <4959FC19.2070404@astronomicalresearchaustralia.org> References: <49556360.000002.20513@kamasutra> <4955853F.4090407@astronomicalresearchaustralia.org> <1230373752.24875.14.camel@scorpion.multitel.be> <49562D88.6090909@astronomicalresearchaustralia.org> <1230409601.30628.0.camel@scorpion.multitel.be> <49571AD4.1010703@astronomicalresearchaustralia.org> <1230487181.4343.0.camel@scorpion.multitel.be> <49582D6C.1040901@astronomicalresearchaustralia.org> <4958A742.9060808@pu-pm.univ-fcomte.fr> <4959FC19.2070404@astronomicalresearchaustralia.org> Message-ID: <495A0019.2080602@astronomicalresearchaustralia.org> Damien, FYI I have just got on to the suse forum to see if I could get some help. Keyed in ekiga and the very first hit I get was somebody saying they have just upgraded to 11.1 and it does not work. Later, Brian PS. I will try to find out who the old packager was and see if they can help. From jmeili at gmx.ch Tue Dec 30 10:22:52 2008 From: jmeili at gmx.ch (Judith Meili) Date: Tue, 30 Dec 2008 11:22:52 +0100 Subject: [Ekiga-list] [Fwd: Re: [Fwd: echo canceller]] In-Reply-To: <1230629712.5078.10.camel@scorpion.multitel.be> References: <495929D4.7090404@gmx.ch> <1230625888.5078.6.camel@scorpion.multitel.be> <4959CEF5.4060800@gmx.ch> <1230629712.5078.10.camel@scorpion.multitel.be> Message-ID: <4959F67C.7020406@gmx.ch> iMac has inbuilt microphone and speaker. Damien Sandras schrieb: > Le mardi 30 d?cembre 2008 ? 08:34 +0100, Judith Meili a ?crit : > >> Thanks. So maybe the microphone is too close to the speaker? Everybody >> complains because of echo. >> >> > > Are the speakers and microphones attached to the same soundcard or do > you use speakers + USB mic or similar ? > From sevmek at free.fr Tue Dec 30 11:40:36 2008 From: sevmek at free.fr (yannick) Date: Tue, 30 Dec 2008 12:40:36 +0100 Subject: [Ekiga-list] 473 Filtered destination In-Reply-To: <4959FF61.000001.20636@kamasutra> References: <4959FF61.000001.20636@kamasutra> Message-ID: <1230637236.32518.38.camel@achille> Le mardi 30 d?cembre 2008 ? 12:00 +0100, Palo S. a ?crit : > I have reproduced the same problem on yet another computer > running Ubuntu with Ekiga 3.0 packaged by Yannick. So my > suspicion on distribution specificity is wrong. I am even > more wondering why nobody else complains about this... > weird. > This is quite an interesting question. I must admit I've seen myself the same issue you reported: my ekiga 3 not being able to accurately display presence for my contacts in the long run. Why I did not reported this? My packs are not latest stable version, I did not have something more accurate than just I can see it did not work all time. In short, I did not believe I had enough to track the bug down efficiently. And I also admit my commitment to this project is sometime weaker... Let's no fall in the mistake of being guilty, but when comparing to other similar projects backed by profit, it is quite depressing. This also raise question about the quality process for Ekiga. I do not count much on our users to perform such testing by themselves, except for obvious bugs like craches, totally broken feature, etc. Fortunately there is people like you taking time to report, but this is not the right way for most people who need a lot of guidance for it and who probably do not have the culture background to clearly see how much feedback is important for us. I congrats you for being so insistant on this issue. Most people would have given up a long time ago. I think we should improve this part of our practise: http://wiki.ekiga.org/index.php/Pre-release_test And I also need to set back up the daily snapshots/last stable for Ubuntu. So many work to do... I think we should: 1- ease the process of reporting issues; waiting for people to show up in the right place, then asking for a -d 4 probably make it harder to report. 2- build up automatic testing/regression test for ekiga Best regards, Yannick From jmeili at gmx.ch Tue Dec 30 11:40:35 2008 From: jmeili at gmx.ch (Judith Meili) Date: Tue, 30 Dec 2008 12:40:35 +0100 Subject: [Ekiga-list] Audio-Problems In-Reply-To: <1230629728.5078.12.camel@scorpion.multitel.be> References: <4959CDCF.7060906@gmx.ch> <1230625841.5078.4.camel@scorpion.multitel.be> <4959CF21.2050302@gmx.ch> <1230629728.5078.12.camel@scorpion.multitel.be> Message-ID: <495A08B3.6040803@gmx.ch> It shouldnt be skype. I need both programs. After restarting it was working again. Damien Sandras schrieb: > It's perhaps skype in that case. > > Le mardi 30 d?cembre 2008 ? 08:34 +0100, Judith Meili a ?crit : > >> Mais par quel program? J'ai aucun program ouvert sauf skype. >> >> Damien Sandras schrieb: >> >>> Hello, >>> >>> Le mardi 30 d?cembre 2008 ? 08:29 +0100, Judith Meili a ?crit : >>> >>> >>>> Hello >>>> >>>> Why do I get this message? >>>> >>>> "Audiokanal zum Audioempfang konnte nicht ge?ffnet werden >>>> >>>> Beim Versuch, Audio f?r den Audio-Empfang ?ber die Soundkarte >>>> auszugeben, ist ein Fehler aufgetreten. Bitte ?berpr?fen Sie, dass die >>>> Soundkarte nicht anderweitig benutzt wird und dass der Treiber >>>> Voll-Duplex unterst?tzt. >>>> Der Audioempfang wurde deaktiviert." >>>> >>>> >>>> >>> La carte son est d?j? occup?e par un autre programme ? >>> >>> >> _______________________________________________ >> ekiga-list mailing list >> ekiga-list at gnome.org >> http://mail.gnome.org/mailman/listinfo/ekiga-list >> From palos at post.sk Tue Dec 30 13:09:12 2008 From: palos at post.sk (Palo S.) Date: 30 Dec 2008 14:09:12 +0100 (CET) Subject: [Ekiga-list] Audio-Problems Message-ID: <495A1D78.000001.31633@kamasutra> > It shouldnt be skype. I need both programs. After restarting it was > working again. Then you should maybe complain to Skype developers? It looks like Skype is blocking Ekiga, not the other way around. It works in the same way for me too, I have to quit Skype otherwise audio in Ekiga does not work. (For me it is no problem, I use Skype rarely.) __________ http://www.inzeraty.sk/ - Bezplatn? inzercia v najob??benej??ch kateg?ri?ch From palos at post.sk Tue Dec 30 14:06:30 2008 From: palos at post.sk (Palo S.) Date: 30 Dec 2008 15:06:30 +0100 (CET) Subject: [Ekiga-list] 473 Filtered destination Message-ID: <495A2AE6.000001.03803@kamasutra> ----- Origin?lna Spr?va ----- Od: yannick Komu: Ekiga mailing list Poslan?: 30.12.2008 12:40 Predmet: Re: [Ekiga-list] 473 Filtered destination > Le mardi 30 d??cembre 2008 ?? 12:00 +0100, Palo S. a ??crit : > > I have reproduced the same problem on yet another computer > > running Ubuntu with Ekiga 3.0 packaged by Yannick. So my > > suspicion on distribution specificity is wrong. I am even > > more wondering why nobody else complains about this... > > weird. > > > > This is quite an interesting question. > > I must admit I\'ve seen myself the same issue you reported: my ekiga 3 > not being able to accurately display presence for my contacts in the > long run. Well, the issue that I reported causes more important problem - it is not possible to reach the client after some time (ie no incoming calls because server rejects them although outcoming work just fine). And this is something I thought people would notice and report... However, wrong presence indication accompanies this issue so maybe you actually do suffer by the same problem? It is easy to see in the logfile: after some time there are no messages at all. Also, the client cannot be closed properly then. > > Why I did not reported this? My packs are not latest stable version, I > did not have something more accurate than just I can see it did not work > all time. In short, I did not believe I had enough to track the bug down > efficiently. And I also admit my commitment to this project is sometime I also noticed more issues but did not report from the same reasons. Presence indication not working correctly after some time was the first I noticed. Then there is video not transmitted when using theora codec in certain cases, h264 not initialized correctly in certain cases, occasional hang of Ekiga when releasing the call... However these issues are clearly not that important and not so reproducible as the one that I reported. > weaker... Let\'s no fall in the mistake of being guilty, but when > comparing to other similar projects backed by profit, it is quite > depressing. Yes, this is clearly a problem. However, I have been using Ekiga 2 for some 2 years for calls with relatives without any major problems and I can say that in my experience and for my purposes it worked significantly better than Skype. And Ekiga 3 is close to fix the remaining smaller problems or missing features I had with 2 (such as cpu getting to 100% with video or missing presence indication). So the state of Ekiga is clearly not that depressing. Given the very limited manpower and free time based development it is actually unbelievable how reliably Ekiga worked for me in the last years. Now with 3.0 and new server more issues emerged and your questions about how these could be prevented are of course very important to ask. > > This also raise question about the quality process for Ekiga. I do not > count much on our users to perform such testing by themselves, except > for obvious bugs like craches, totally broken feature, etc. Fortunately > there is people like you taking time to report, but this is not the > right way for most people who need a lot of guidance for it and who > probably do not have the culture background to clearly see how much > feedback is important for us. > > I congrats you for being so insistant on this issue. Most people would > have given up a long time ago. Well, suddenly my relatives started to complain that they cannot call me and I also noticed I could not call them sometimes. That was enough to convince even a lazy man like me to have a closer look and report my findings :) > > I think we should improve this part of our practise: > http://wiki.ekiga.org/index.php/Pre-release_test > > And I also need to set back up the daily snapshots/last stable for > Ubuntu. So many work to do... > > I think we should: > 1- ease the process of reporting issues; waiting for people to show up > in the right place, then asking for a -d 4 probably make it harder to > report. > 2- build up automatic testing/regression test for ekiga I am sure both these points would help a lot. Regarding 1, I can think of several improvements (note that I am not Ekiga developer so some of these may be wrong/ not possible/not feasible etc): a) It should be possible to send the data from crash directly to Ekiga developers with one click. Similar thing as eg Firefox handles this. Maybe it is already intended but when I get a crash, I only get the possiblity to save the log and send it to an email address - hard to imagine that a usual user would do that. b) There could be an option in the GUI to deal with problems and their reports. This would enable the user to turn on/off log catching and in case it is turned on, to send it as well as the report directly from the client. Regarding 2, certainly something that would be very useful. It could certainly not catch all the possible problems but could still help a lot. At the beginning, something simple like automatic periodic trunk/stable compilation, running 2 instances on 2 locations and their automated periodic call making with detection of incoming sound and presence indication checked by sending parallel messages between these two computers could be of big help. Ssome other things could be automatically tested also. However, all of these would clearly take a _huge_ amount of time... Palo __________ http://cestovanie.sme.sk/ - Cel? svet na va?om monitore From opeyer at nimr.mrc.ac.uk Tue Dec 30 13:52:28 2008 From: opeyer at nimr.mrc.ac.uk (opeyer at nimr.mrc.ac.uk) Date: Tue, 30 Dec 2008 13:52:28 +0000 Subject: [Ekiga-list] [Fwd: Re: [Fwd: echo canceller]] Message-ID: <1528055605-1230645680-cardhu_decombobulator_blackberry.rim.net-1668076608-@bxe079.bisx.produk.on.blackberry> This is basically a simple acoustic issue with the iMac since the microphone and speaker are pretty close together in the same case = echo between them. I got around it by using a separate microphone OR earphones - you only need one of the two. This is enough to stop the echo. You could even do it wirelessly if your model supports Bluetooth headsets. Oliver ------Original Message------ From: Judith Meili Sender: ekiga-list-bounces at gnome.org To: Ekiga mailing list ReplyTo: Ekiga mailing list Subject: Re: [Ekiga-list] [Fwd: Re: [Fwd: echo canceller]] Sent: 30 Dec 2008 10:22 iMac has inbuilt microphone and speaker. Damien Sandras schrieb: > Le mardi 30 d?cembre 2008 ? 08:34 +0100, Judith Meili a ?crit : > >> Thanks. So maybe the microphone is too close to the speaker? Everybody >> complains because of echo. >> >> > > Are the speakers and microphones attached to the same soundcard or do > you use speakers + USB mic or similar ? > _______________________________________________ ekiga-list mailing list ekiga-list at gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list ------------------ Oliver de Peyer PhD Lab 209 Division of Molecular Structure National Institute for Medical Research The Ridgeway Mill Hill London NW71AA United Kingdom Tel 0208 816 2688 Fax 0208 816 2580 Mobile phone +44 7908 783367 opeyer at nimr.mrc.ac.uk From palos at post.sk Tue Dec 30 14:20:13 2008 From: palos at post.sk (Palo S.) Date: 30 Dec 2008 15:20:13 +0100 (CET) Subject: [Ekiga-list] 473 Filtered destination Message-ID: <495A2E1D.000001.05051@kamasutra> > > Can you try to remove from your contact list all things related to > ekiga.net : 500 at ekiga.net, 501 at ekiga.net and so on ? > You can keep your normal contacts. Looks like a good shot! Running for two hours now and still ok. Also the amount of traffic is much smaller. The log is 400k now while it used to be maybe 40M at this time with 500 and 501 in contact list. I still cannot confirm with 100% though, I will try on another computer and for longer time and let you know. Palo __________ Mobiln? telef?ny v slovenskej premi?re a najaktu?lnej?ie inform?cie - http://mobil.sme.sk/ From dsandras at seconix.com Tue Dec 30 14:20:10 2008 From: dsandras at seconix.com (Damien Sandras) Date: Tue, 30 Dec 2008 15:20:10 +0100 Subject: [Ekiga-list] 473 Filtered destination In-Reply-To: <495A2E1D.000001.05051@kamasutra> References: <495A2E1D.000001.05051@kamasutra> Message-ID: <1230646810.5078.46.camel@scorpion.multitel.be> Le mardi 30 d?cembre 2008 ? 15:20 +0100, Palo S. a ?crit : > > > > Can you try to remove from your contact list all things related to > > ekiga.net : 500 at ekiga.net, 501 at ekiga.net and so on ? > > You can keep your normal contacts. > > Looks like a good shot! Running for two hours now and > still ok. Also the amount of traffic is much smaller. > The log is 400k now while it used to be maybe 40M at > this time with 500 and 501 in contact list. > I still cannot confirm with 100% though, I will try > on another computer and for longer time and let you > know. > There is a bug in Asterisk on ekiga.net, I need to find a workaround tonight. I don't think Ekiga is faulty there. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From palos at post.sk Tue Dec 30 14:43:08 2008 From: palos at post.sk (Palo S.) Date: 30 Dec 2008 15:43:08 +0100 (CET) Subject: [Ekiga-list] 473 Filtered destination Message-ID: <495A337C.000001.06783@kamasutra> ----- Origin?lna Spr?va ----- Od: Damien Sandras Komu: Ekiga mailing list Poslan?: 30.12.2008 15:20 Predmet: Re: [Ekiga-list] 473 Filtered destination > Le mardi 30 d??cembre 2008 ?? 15:20 +0100, Palo S. a ??crit : > > > > > > Can you try to remove from your contact list all things related to > > > ekiga.net : 500 at ekiga.net, 501 at ekiga.net and so on ? > > > You can keep your normal contacts. > > > > Looks like a good shot! Running for two hours now and > > still ok. Also the amount of traffic is much smaller. > > The log is 400k now while it used to be maybe 40M at > > this time with 500 and 501 in contact list. > > I still cannot confirm with 100% though, I will try > > on another computer and for longer time and let you > > know. > > > > There is a bug in Asterisk on ekiga.net, I need to find a workaround > tonight. I don\'t think Ekiga is faulty there. I was suspecting it could be ekiga.net issue again a.o. because I started to use Ekiga 3.0 longer time ago and this problem only appeared relatively recently. Very good that finally we are getting close to the problem localization! 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:dsandras at ekiga.net > > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list __________ Mozaika storo?ia denn?ka SME - http://mozaika.sme.sk From palos at post.sk Tue Dec 30 16:55:21 2008 From: palos at post.sk (Palo S.) Date: 30 Dec 2008 17:55:21 +0100 (CET) Subject: [Ekiga-list] 473 Filtered destination Message-ID: <495A5279.000001.17485@kamasutra> > > Le mardi 30 d??cembre 2008 ?? 15:20 +0100, Palo S. a ??crit : > > > > > > > > Can you try to remove from your contact list all things related to > > > > ekiga.net : 500 at ekiga.net, 501 at ekiga.net and so on ? > > > > You can keep your normal contacts. > > > > > > Looks like a good shot! Running for two hours now and > > > still ok. Also the amount of traffic is much smaller. > > > The log is 400k now while it used to be maybe 40M at > > > this time with 500 and 501 in contact list. > > > I still cannot confirm with 100% though, I will try > > > on another computer and for longer time and let you > > > know. > > > I can confirm now - the problem disappears after I remove ekiga.net related contacts from contact list. Palo __________ http://www.tahaj.sk - Najnavstevovanejsia stranka slovenskeho downloadu From dsandras at seconix.com Tue Dec 30 16:48:05 2008 From: dsandras at seconix.com (Damien Sandras) Date: Tue, 30 Dec 2008 17:48:05 +0100 Subject: [Ekiga-list] 473 Filtered destination In-Reply-To: <495A5279.000001.17485@kamasutra> References: <495A5279.000001.17485@kamasutra> Message-ID: <1230655685.5078.48.camel@scorpion.multitel.be> Le mardi 30 d?cembre 2008 ? 17:55 +0100, Palo S. a ?crit : > > > Le mardi 30 d??cembre 2008 ? 15:20 +0100, Palo S. a ??crit : > > > > > > > > > > Can you try to remove from your contact list all things related to > > > > > ekiga.net : 500 at ekiga.net, 501 at ekiga.net and so on ? > > > > > You can keep your normal contacts. > > > > > > > > Looks like a good shot! Running for two hours now and > > > > still ok. Also the amount of traffic is much smaller. > > > > The log is 400k now while it used to be maybe 40M at > > > > this time with 500 and 501 in contact list. > > > > I still cannot confirm with 100% though, I will try > > > > on another computer and for longer time and let you > > > > know. > > > > > > I can confirm now - the problem disappears after I remove > ekiga.net related contacts from contact list. > Excellent, I'll find an alternative then. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From jmeili at gmx.ch Tue Dec 30 16:03:01 2008 From: jmeili at gmx.ch (Judith Meili) Date: Tue, 30 Dec 2008 17:03:01 +0100 Subject: [Ekiga-list] [Fwd: Re: [Fwd: echo canceller]] In-Reply-To: <1528055605-1230645680-cardhu_decombobulator_blackberry.rim.net-1668076608-@bxe079.bisx.produk.on.blackberry> References: <1528055605-1230645680-cardhu_decombobulator_blackberry.rim.net-1668076608-@bxe079.bisx.produk.on.blackberry> Message-ID: <495A4635.9050102@gmx.ch> In other words "Apple sells rubbish". Correct? opeyer at nimr.mrc.ac.uk schrieb: > This is basically a simple acoustic issue with the iMac since the microphone and speaker are pretty close together in the same case = echo between them. I got around it by using a separate microphone OR earphones - you only need one of the two. This is enough to stop the echo. You could even do it wirelessly if your model supports Bluetooth headsets. > Oliver > > ------Original Message------ > From: Judith Meili > Sender: ekiga-list-bounces at gnome.org > To: Ekiga mailing list > ReplyTo: Ekiga mailing list > Subject: Re: [Ekiga-list] [Fwd: Re: [Fwd: echo canceller]] > Sent: 30 Dec 2008 10:22 > > iMac has inbuilt microphone and speaker. > > > Damien Sandras schrieb: > >> Le mardi 30 d?cembre 2008 ? 08:34 +0100, Judith Meili a ?crit : >> >> >>> Thanks. So maybe the microphone is too close to the speaker? Everybody >>> complains because of echo. >>> >>> >>> >> Are the speakers and microphones attached to the same soundcard or do >> you use speakers + USB mic or similar ? >> >> > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > > ------------------ > Oliver de Peyer PhD > Lab 209 > Division of Molecular Structure > National Institute for Medical Research > The Ridgeway > Mill Hill > London > NW71AA > United Kingdom > Tel 0208 816 2688 > Fax 0208 816 2580 > Mobile phone +44 7908 783367 > opeyer at nimr.mrc.ac.uk > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > > From Eugen.Dedu at pu-pm.univ-fcomte.fr Tue Dec 30 17:17:45 2008 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Tue, 30 Dec 2008 18:17:45 +0100 Subject: [Ekiga-list] Compile Problem In-Reply-To: <4959FC19.2070404@astronomicalresearchaustralia.org> References: <49556360.000002.20513@kamasutra> <4955853F.4090407@astronomicalresearchaustralia.org> <1230373752.24875.14.camel@scorpion.multitel.be> <49562D88.6090909@astronomicalresearchaustralia.org> <1230409601.30628.0.camel@scorpion.multitel.be> <49571AD4.1010703@astronomicalresearchaustralia.org> <1230487181.4343.0.camel@scorpion.multitel.be> <49582D6C.1040901@astronomicalresearchaustralia.org> <4958A742.9060808@pu-pm.univ-fcomte.fr> <4959FC19.2070404@astronomicalresearchaustralia.org> Message-ID: <495A57B9.9050206@pu-pm.univ-fcomte.fr> Brian wrote: > Eugen, > Thanks this put me on the right track. > I can confirm that suse 11.1 is the problem. > > In ekiga-3.0.1/lib/engine/ it still uses *.la files all these have been > removed in 11.1, in addition there is practically nothing in > /opt/gnome/lib. Most of those files have been moved to /usr/lib. > There were about 6 other files that were deleted altogether. > What a mess! > Anyway I got over all of them, and engine compiled ok. > > Now I get to > /usr/lib/gcc/i586-suse-linux/4.3/../../../../i586-suse-linux/bin/ld: > cannot find -lresmgr > collect2: ld returned 1 exit status > make[3]: *** [ekiga] Error 1 > make[3]: Leaving directory `/Documents/SOURCE/SUSE11/ekiga-3.0.1/src' > make[2]: *** [all] Error 2 > make[2]: Leaving directory `/Documents/SOURCE/SUSE11/ekiga-3.0.1/src' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/Documents/SOURCE/SUSE11/ekiga-3.0.1' > make: *** [all] Error 2 > > Only to discover that suse dropped support for resmgr after 10.3. > It nolonger exists in 11.1. Suse now appears to use hal-resmgr. > > Once I figured out what libs were required where, I coped, but I do not > understand how to proceed with this one. > Is it possible to remove the requirement to load resmgr? Hi, I didn't know what resmgr is, so I took a look at http://www.lst.de/~okir/resmgr. In debian, my machine, resmgr does not exist. I searched resmgr in ekiga, ptlib and opal, and I haven't found it either. So I imagine it's suse which adds it to the command line?? Look at the parameters of gcc (gcc -v or other flags, I don't know). Also, try to install the package providing resmgr library. -- Eugen From stefan at lucke.in-berlin.de Tue Dec 30 17:39:13 2008 From: stefan at lucke.in-berlin.de (Stefan Lucke) Date: Tue, 30 Dec 2008 18:39:13 +0100 Subject: [Ekiga-list] Colour format not supported with ekiga-svn Message-ID: <200812301839.13422.stefan@lucke.in-berlin.de> Hi, I'm trying current svn version of ekiga & co (was a checkout from yesterday). My camera 'logitech quickcam connect' (046d:08d9) works quite well with ekiga 2.0.11, 2.0.12, 3.0.1 but unfortunately not with current svn. Message from error-box is: "Your driver doesn't seem to support any of the color formats supported by Ekiga. Please check your kernel driver documentation in order to determine which Palette is supported. ..." From kernel v4l-dvb driver: v4l-dvb/linux/drivers/media/video/gspca/zc3xx.c: static struct v4l2_pix_format vga_mode[] = { {320, 240, V4L2_PIX_FMT_JPEG, V4L2_FIELD_NONE, .bytesperline = 320, .sizeimage = 320 * 240 * 3 / 8 + 590, .colorspace = V4L2_COLORSPACE_JPEG, .priv = 1}, {640, 480, V4L2_PIX_FMT_JPEG, V4L2_FIELD_NONE, .bytesperline = 640, .sizeimage = 640 * 480 * 3 / 8 + 590, .colorspace = V4L2_COLORSPACE_JPEG, .priv = 0}, }; static struct v4l2_pix_format sif_mode[] = { {176, 144, V4L2_PIX_FMT_JPEG, V4L2_FIELD_NONE, .bytesperline = 176, .sizeimage = 176 * 144 * 3 / 8 + 590, .colorspace = V4L2_COLORSPACE_JPEG, .priv = 1}, {352, 288, V4L2_PIX_FMT_JPEG, V4L2_FIELD_NONE, .bytesperline = 352, .sizeimage = 352 * 288 * 3 / 8 + 590, .colorspace = V4L2_COLORSPACE_JPEG, .priv = 0}, }; Should I get a new cam? For successfully compiling opal with my ffmpeg version, I had to apply the attached patch. -- Stefan Lucke -------------- next part -------------- Index: plugins/video/H.263-1998/h263-1998.cxx =================================================================== --- plugins/video/H.263-1998/h263-1998.cxx (revision 21872) +++ plugins/video/H.263-1998/h263-1998.cxx (working copy) @@ -450,14 +450,20 @@ if (!H263_Base_EncoderContext::Open(CODEC_ID_H263)) return false; +#if LIBAVCODEC_VERSION_INT < ((52<<16)+(0<<8)+0) _context->rtp_mode = 1; +#endif _context->rtp_payload_size = 200; _context->rtp_callback = &rtp_callback; _context->opaque = (H263_RFC2190_EncoderContext *)this; // used to separate out packets from different encode threads _context->flags &= ~CODEC_FLAG_H263P_UMV; _context->flags &= ~CODEC_FLAG_4MV; +#if LIBAVCODEC_VERSION_INT < ((52<<16)+(0<<8)+0) _context->flags &= ~CODEC_FLAG_H263P_AIC; +#else + _context->flags &= ~CODEC_FLAG_AC_PRED; +#endif _context->flags &= ~CODEC_FLAG_H263P_AIV; _context->flags &= ~CODEC_FLAG_H263P_SLICE_STRUCT; From dsandras at seconix.com Tue Dec 30 18:27:51 2008 From: dsandras at seconix.com (Damien Sandras) Date: Tue, 30 Dec 2008 19:27:51 +0100 Subject: [Ekiga-list] Colour format not supported with ekiga-svn In-Reply-To: <200812301839.13422.stefan@lucke.in-berlin.de> References: <200812301839.13422.stefan@lucke.in-berlin.de> Message-ID: <1230661671.4514.0.camel@scorpion.multitel.be> Hi, Le mardi 30 d?cembre 2008 ? 18:39 +0100, Stefan Lucke a ?crit : > Hi, > > I'm trying current svn version of ekiga & co (was a checkout from yesterday). > My camera 'logitech quickcam connect' (046d:08d9) works quite well > with ekiga 2.0.11, 2.0.12, 3.0.1 but unfortunately not with current svn. > Did you compile PTLIB with libv4l support ? Most probably ekiga 2.0.11 were compiled with libv4l support but not TRUNK, which would explain this problem. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From stefan at lucke.in-berlin.de Tue Dec 30 19:02:25 2008 From: stefan at lucke.in-berlin.de (Stefan Lucke) Date: Tue, 30 Dec 2008 20:02:25 +0100 Subject: [Ekiga-list] Colour format not supported with ekiga-svn In-Reply-To: <1230661671.4514.0.camel@scorpion.multitel.be> References: <200812301839.13422.stefan@lucke.in-berlin.de> <1230661671.4514.0.camel@scorpion.multitel.be> Message-ID: <200812302002.25542.stefan@lucke.in-berlin.de> On Tuesday 30 December 2008, Damien Sandras wrote: > Hi, > > > Le mardi 30 d?cembre 2008 ? 18:39 +0100, Stefan Lucke a ?crit : > > Hi, > > > > I'm trying current svn version of ekiga & co (was a checkout from yesterday). > > My camera 'logitech quickcam connect' (046d:08d9) works quite well > > with ekiga 2.0.11, 2.0.12, 3.0.1 but unfortunately not with current svn. > > > > Did you compile PTLIB with libv4l support ? I think I did so: stefan at jarada /home/nfs/extra/src/video/Ekiga/Ekiga-2008-12-29/ptlib $ grep v4l config.log $ ./configure --prefix=/usr --enable-v4l --enable-v4l2 configure:16342: running /bin/sh ./configure '--prefix=/usr' '--enable-v4l' '--enable-v4l2' --cache-file=/dev/null --srcdir=. > > Most probably ekiga 2.0.11 were compiled with libv4l support but not > TRUNK, which would explain this problem. From ekiga -d 5 and a slightly modified ptlib I get the following output: 1195724874 = 0x4745504A => GEPJ (JPEG) 842093913 = 0x32315559 => 21UY (YU12) 2008/12/30 19:58:23.700 0:00.757 Detecting V4L2 devices 2008/12/30 19:58:23.700 0:00.757 PV4L2Plugin detected device metadata at /sys/class/video4linux/ 2008/12/30 19:58:23.700 0:00.757 PV4L2Plugin detected capture device USB Camera (046d:08d9) 2008/12/30 19:58:23.700 0:00.757 PVidInDev Open() devName:/dev/video0 videoFd:-1 2008/12/30 19:58:23.700 0:00.757 PVidInDev G_PARM failed (preserving frame rate may not work) : Invalid argument 2008/12/30 19:58:23.700 0:00.757 PVidInDev colour format mismatch. (1195724874,842093913). 2008/12/30 19:58:23.700 0:00.757 PVidDev SetColourFormatConverter, want YUV420P trying YUV420P 2008/12/30 19:58:23.701 0:00.758 PVidInDev G_PARM failed (preserving frame rate may not work) : Invalid argument 2008/12/30 19:58:23.701 0:00.758 PVidInDev colour format mismatch. (1195724874,842093913). 2008/12/30 19:58:23.701 0:00.758 PVidDev SetColourFormatConverter, want YUV420P trying I420 2008/12/30 19:58:23.701 0:00.758 PVidDev SetColourFormatConverter, want YUV420P trying IYUV 2008/12/30 19:58:23.701 0:00.758 PVidDev SetColourFormatConverter, want YUV420P trying YUV420 2008/12/30 19:58:23.701 0:00.758 PVidInDev G_PARM failed (preserving frame rate may not work) : Invalid argument 2008/12/30 19:58:23.701 0:00.758 PVidInDev colour format mismatch. (1195724874,825382478). 2008/12/30 19:58:23.701 0:00.758 PVidDev SetColourFormatConverter, want YUV420P trying RGB32 2008/12/30 19:58:23.701 0:00.758 PVidInDev G_PARM failed (preserving frame rate may not work) : Invalid argument 2008/12/30 19:58:23.701 0:00.758 PVidInDev colour format mismatch. (1195724874,876758866). 2008/12/30 19:58:23.701 0:00.758 PVidDev SetColourFormatConverter, want YUV420P trying BGR32 2008/12/30 19:58:23.701 0:00.758 PVidInDev G_PARM failed (preserving frame rate may not work) : Invalid argument 2008/12/30 19:58:23.701 0:00.758 PVidInDev colour format mismatch. (1195724874,877807426). 2008/12/30 19:58:23.701 0:00.758 PVidDev SetColourFormatConverter, want YUV420P trying RGB24 2008/12/30 19:58:23.701 0:00.758 PVidInDev G_PARM failed (preserving frame rate may not work) : Invalid argument 2008/12/30 19:58:23.701 0:00.758 PVidInDev colour format mismatch. (1195724874,859981650). 2008/12/30 19:58:23.701 0:00.758 PVidDev SetColourFormatConverter, want YUV420P trying BGR24 2008/12/30 19:58:23.701 0:00.758 PVidInDev G_PARM failed (preserving frame rate may not work) : Invalid argument 2008/12/30 19:58:23.701 0:00.758 PVidInDev colour format mismatch. (1195724874,861030210). 2008/12/30 19:58:23.701 0:00.758 PVidDev SetColourFormatConverter, want YUV420P trying YUY2 2008/12/30 19:58:23.701 0:00.758 PVidInDev G_PARM failed (preserving frame rate may not work) : Invalid argument 2008/12/30 19:58:23.701 0:00.758 PVidInDev colour format mismatch. (1195724874,1448695129). 2008/12/30 19:58:23.701 0:00.758 PVidDev SetColourFormatConverter, want YUV420P trying YUV422 2008/12/30 19:58:23.701 0:00.758 PVidInDev G_PARM failed (preserving frame rate may not work) : Invalid argument 2008/12/30 19:58:23.701 0:00.758 PVidInDev colour format mismatch. (1195724874,1448695129). 2008/12/30 19:58:23.701 0:00.758 PVidDev SetColourFormatConverter, want YUV420P trying YUV422P 2008/12/30 19:58:23.701 0:00.758 PVidInDev G_PARM failed (preserving frame rate may not work) : Invalid argument 2008/12/30 19:58:23.701 0:00.758 PVidInDev colour format mismatch. (1195724874,1345466932). 2008/12/30 19:58:23.701 0:00.758 PVidDev SetColourFormatConverter, want YUV420P trying YUV411 2008/12/30 19:58:23.701 0:00.758 PVidInDev G_PARM failed (preserving frame rate may not work) : Invalid argument 2008/12/30 19:58:23.701 0:00.758 PVidInDev colour format mismatch. (1195724874,1345401945). 2008/12/30 19:58:23.701 0:00.758 PVidDev SetColourFormatConverter, want YUV420P trying YUV411P 2008/12/30 19:58:23.701 0:00.758 PVidInDev G_PARM failed (preserving frame rate may not work) : Invalid argument 2008/12/30 19:58:23.701 0:00.758 PVidInDev colour format mismatch. (1195724874,1345401140). 2008/12/30 19:58:23.701 0:00.758 PVidDev SetColourFormatConverter, want YUV420P trying RGB565 2008/12/30 19:58:23.701 0:00.758 PVidInDev G_PARM failed (preserving frame rate may not work) : Invalid argument 2008/12/30 19:58:23.701 0:00.758 PVidInDev colour format mismatch. (1195724874,1346520914). 2008/12/30 19:58:23.701 0:00.758 PVidDev SetColourFormatConverter, want YUV420P trying RGB555 2008/12/30 19:58:23.701 0:00.758 PVidInDev G_PARM failed (preserving frame rate may not work) : Invalid argument 2008/12/30 19:58:23.701 0:00.758 PVidInDev colour format mismatch. (1195724874,1329743698). 2008/12/30 19:58:23.701 0:00.758 PVidDev SetColourFormatConverter, want YUV420P trying YUV410 2008/12/30 19:58:23.701 0:00.758 PVidDev SetColourFormatConverter, want YUV420P trying YUV410P 2008/12/30 19:58:23.701 0:00.758 PVidDev SetColourFormatConverter, want YUV420P trying Grey 2008/12/30 19:58:23.701 0:00.758 PVidInDev G_PARM failed (preserving frame rate may not work) : Invalid argument 2008/12/30 19:58:23.701 0:00.758 PVidInDev colour format mismatch. (1195724874,1497715271). 2008/12/30 19:58:23.701 0:00.758 PVidDev SetColourFormatConverter, want YUV420P trying GreyF 2008/12/30 19:58:23.701 0:00.758 PVidDev SetColourFormatConverter, want YUV420P trying UYVY422 2008/12/30 19:58:23.702 0:00.759 PVidInDev G_PARM failed (preserving frame rate may not work) : Invalid argument 2008/12/30 19:58:23.702 0:00.759 PVidInDev colour format mismatch. (1195724874,1498831189). 2008/12/30 19:58:23.702 0:00.759 PVidDev SetColourFormatConverter, want YUV420P trying UYV444 2008/12/30 19:58:23.702 0:00.759 PVidDev SetColourFormatConverter, want YUV420P trying SBGGR8 2008/12/30 19:58:23.702 0:00.759 PVidInDev G_PARM failed (preserving frame rate may not work) : Invalid argument 2008/12/30 19:58:23.702 0:00.759 PVidInDev colour format mismatch. (1195724874,825770306). 2008/12/30 19:58:23.702 0:00.759 PVidDev SetColourFormatConverter FAILED for YUV420P 2008/12/30 19:58:23.702 0:00.759 GMVideoInputManager_ptlib Encountered error 4 while opening device 2008/12/30 19:58:23.702 0:00.759 VidInputCore Falling back to Moving Logo (Moving Logo/Moving Logo) -- Stefan Lucke From jmeili at gmx.ch Tue Dec 30 18:16:00 2008 From: jmeili at gmx.ch (Judith Meili) Date: Tue, 30 Dec 2008 19:16:00 +0100 Subject: [Ekiga-list] direct phonecall by clicking on a phone number in the white pages Message-ID: <495A6560.5030307@gmx.ch> hello When I click on a phone number in http://tel.local.ch/ it wrights automatically the number in Ekiga like this: callto://+41317355755 Then I always have to delete "callto://+" and write sip:0041317355755. Why does it change to "callto://+". It would be very convenient if it stays like "sip:00" Thanks. Br jm From Eugen.Dedu at pu-pm.univ-fcomte.fr Tue Dec 30 19:39:54 2008 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Tue, 30 Dec 2008 20:39:54 +0100 Subject: [Ekiga-list] Debian packages In-Reply-To: <20081221203342.GT5641@niof.net> References: <494E9244.4030701@pu-pm.univ-fcomte.fr> <20081221203342.GT5641@niof.net> Message-ID: <495A790A.1010002@pu-pm.univ-fcomte.fr> Rick Pasotto wrote: > gnome-desktop-environment depends on ekiga (>= 2.0.12) > > Since 'aptitude install ekiga-snapshot' removes ekiga, > gnome-desktop-environment becomes BROKEN and the installation > would REMOVE 47 other packages. > > As far as I'm concerned, this means that ekiga-snapshot is NOT > installable. > > I think that the problem is that the version number for ekiga-snapshot > is 0-20081220-1 which is less than 2.0.12. Perhaps if the version number > were changed to something greater that 2.0.12 (eg, 3-20081220-1) then > the problem would go away. Hi, Increasing the version of ekiga-snapshot does not work. There are two solutions: - either stay as we are now. Note that only gnome-desktop-environment is removed (+old pwlwib/opal), not 47 packages!! - or do not use ekiga-snapshot anymore, but ekiga (while ptlib and opal are still named -snapshot, to avoid soname problems). Note that this will not be intrusive or conflict with debian package, because the version will be carefully chosen. What do people prefer?? -- Eugen From ml at stdout.at Tue Dec 30 20:12:47 2008 From: ml at stdout.at (Hannes Ebner) Date: Tue, 30 Dec 2008 21:12:47 +0100 Subject: [Ekiga-list] Debian packages In-Reply-To: <495A790A.1010002@pu-pm.univ-fcomte.fr> References: <494E9244.4030701@pu-pm.univ-fcomte.fr> <20081221203342.GT5641@niof.net> <495A790A.1010002@pu-pm.univ-fcomte.fr> Message-ID: <495A80BF.30001@stdout.at> Eugen Dedu wrote: > There are two solutions: > - either stay as we are now. Note that only gnome-desktop-environment > is removed (+old pwlwib/opal), not 47 packages!! > - or do not use ekiga-snapshot anymore, but ekiga (while ptlib and opal > are still named -snapshot, to avoid soname problems). Note that this > will not be intrusive or conflict with debian package, because the > version will be carefully chosen. What about a third solution, namely adding a "provides" statement to the package definition of ekiga-snapshot? I.e. "Provides: ekiga". See . AFAIK this approach is widely used, one example is the thunderbird package which has a "Provides: mail-reader". HTH, Hannes From rick at niof.net Tue Dec 30 20:13:39 2008 From: rick at niof.net (Rick Pasotto) Date: Tue, 30 Dec 2008 15:13:39 -0500 Subject: [Ekiga-list] Debian packages In-Reply-To: <495A790A.1010002@pu-pm.univ-fcomte.fr> References: <494E9244.4030701@pu-pm.univ-fcomte.fr> <20081221203342.GT5641@niof.net> <495A790A.1010002@pu-pm.univ-fcomte.fr> Message-ID: <20081230201339.GO5641@niof.net> On Tue, Dec 30, 2008 at 08:39:54PM +0100, Eugen Dedu wrote: > Rick Pasotto wrote: >> gnome-desktop-environment depends on ekiga (>= 2.0.12) >> >> Since 'aptitude install ekiga-snapshot' removes ekiga, >> gnome-desktop-environment becomes BROKEN and the installation would >> REMOVE 47 other packages. >> >> As far as I'm concerned, this means that ekiga-snapshot is NOT >> installable. >> >> I think that the problem is that the version number for >> ekiga-snapshot is 0-20081220-1 which is less than 2.0.12. Perhaps if >> the version number were changed to something greater that 2.0.12 (eg, >> 3-20081220-1) then the problem would go away. > > Hi, > > Increasing the version of ekiga-snapshot does not work. > > There are two solutions: - either stay as we are now. Note that only > gnome-desktop-environment is removed (+old pwlwib/opal), not 47 > packages!! - or do not use ekiga-snapshot anymore, but ekiga (while > ptlib and opal are still named -snapshot, to avoid soname problems). > Note that this will not be intrusive or conflict with debian package, > because the version will be carefully chosen. > > What do people prefer?? Sorry to hear that changing the version number doesn't work. I'm not really clear on exactly how the debian version number punctuation works. Did you try using 3.0.0 or even 2.9? Perhaps the fact that the first non-digit character is a '-' makes a difference. The number of packages that depend on gnome-desktop-environment will vary from system to system. On my machine the following 45 packages would be removed: arj{u} at-spi{u} cheese{u} dasher{u} dasher-data{u} dmz-cursor-theme{u} eog{u} festival{u} festlex-cmu{u} festlex-poslex{u} festvox-kallpc16k{u} file-roller{u} gcalctool{u} gconf-editor{u} gedit{u} gedit-common{u} gnome-accessibility{u} gnome-accessibility-themes{u} gnome-core{u} gnome-desktop-environment gnome-network-admin{u} gnome-orca{u} gnome-power-manager{u} gnome-screensaver{u} gnome-themes{u} gok{u} gstreamer0.10-tools{u} gucharmap{u} iceweasel-gnome-support{u} libalut0{u} libavahi-ui0{u} libbrlapi0.5{u} libglew1.5{u} libgnome-speech7{u} libgtk-vnc-1.0-0{u} libswfdec-0.6-90{u} libxevie1{u} mousetweaks{u} python-brlapi{u} python-gtksourceview2{u} python-pyatspi{u} rss-glx{u} swfdec-gnome{u} unace{u} vinagre{u} I guess I'll have to stay with 2.0.12. -- "He who has never hoped can never despair." -- George Bernard Shaw Rick Pasotto rick at niof.net http://www.niof.net From rick at niof.net Tue Dec 30 20:15:41 2008 From: rick at niof.net (Rick Pasotto) Date: Tue, 30 Dec 2008 15:15:41 -0500 Subject: [Ekiga-list] Debian packages In-Reply-To: <495A80BF.30001@stdout.at> References: <494E9244.4030701@pu-pm.univ-fcomte.fr> <20081221203342.GT5641@niof.net> <495A790A.1010002@pu-pm.univ-fcomte.fr> <495A80BF.30001@stdout.at> Message-ID: <20081230201541.GP5641@niof.net> On Tue, Dec 30, 2008 at 09:12:47PM +0100, Hannes Ebner wrote: > Eugen Dedu wrote: > > There are two solutions: - either stay as we are now. Note that > > only gnome-desktop-environment is removed (+old pwlwib/opal), not 47 > > packages!! - or do not use ekiga-snapshot anymore, but ekiga (while > > ptlib and opal are still named -snapshot, to avoid soname problems). > > Note that this will not be intrusive or conflict with debian > > package, because the version will be carefully chosen. > > What about a third solution, namely adding a "provides" statement to > the package definition of ekiga-snapshot? I.e. "Provides: ekiga". > > See . > > AFAIK this approach is widely used, one example is the thunderbird > package which has a "Provides: mail-reader". The 'provides' is already there. Can the provides include a version number? -- "An avidity to punish is always dangerous to liberty. It leads men to stretch, to misinterpret, and to misapply even the best of laws. He that would make his own liberty secure must guard even his enemy from oppression: for if he violates his duty he establishes a precedent that will reach to himself." -- Thomas Paine, 1795 Rick Pasotto rick at niof.net http://www.niof.net From dsandras at seconix.com Tue Dec 30 20:26:54 2008 From: dsandras at seconix.com (Damien Sandras) Date: Tue, 30 Dec 2008 21:26:54 +0100 Subject: [Ekiga-list] direct phonecall by clicking on a phone number in the white pages In-Reply-To: <495A6560.5030307@gmx.ch> References: <495A6560.5030307@gmx.ch> Message-ID: <1230668814.4514.5.camel@scorpion.multitel.be> Le mardi 30 d?cembre 2008 ? 19:16 +0100, Judith Meili a ?crit : > hello > > When I click on a phone number in http://tel.local.ch/ it wrights > automatically the number in Ekiga like this: callto://+41317355755 > > Then I always have to delete "callto://+" and write sip:0041317355755. > > Why does it change to "callto://+". It would be very convenient if it > stays like "sip:00" > It is a setting of your browser or desktop environment, but I do not know which one. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From dsandras at seconix.com Tue Dec 30 20:28:08 2008 From: dsandras at seconix.com (Damien Sandras) Date: Tue, 30 Dec 2008 21:28:08 +0100 Subject: [Ekiga-list] Colour format not supported with ekiga-svn In-Reply-To: <200812302002.25542.stefan@lucke.in-berlin.de> References: <200812301839.13422.stefan@lucke.in-berlin.de> <1230661671.4514.0.camel@scorpion.multitel.be> <200812302002.25542.stefan@lucke.in-berlin.de> Message-ID: <1230668888.4514.8.camel@scorpion.multitel.be> Le mardi 30 d?cembre 2008 ? 20:02 +0100, Stefan Lucke a ?crit : > On Tuesday 30 December 2008, Damien Sandras wrote: > > Hi, > > > > > > Le mardi 30 d?cembre 2008 ? 18:39 +0100, Stefan Lucke a ?crit : > > > Hi, > > > > > > I'm trying current svn version of ekiga & co (was a checkout from yesterday). > > > My camera 'logitech quickcam connect' (046d:08d9) works quite well > > > with ekiga 2.0.11, 2.0.12, 3.0.1 but unfortunately not with current svn. > > > > > > > Did you compile PTLIB with libv4l support ? > > I think I did so: > > stefan at jarada /home/nfs/extra/src/video/Ekiga/Ekiga-2008-12-29/ptlib $ grep v4l config.log > $ ./configure --prefix=/usr --enable-v4l --enable-v4l2 > configure:16342: running /bin/sh ./configure '--prefix=/usr' '--enable-v4l' '--enable-v4l2' --cache-file=/dev/null --srcdir=. You are confusing 'building the V4L2' plugin and 'building the V4L2 plugin with libv4l'. Libv4l is an external library that our V4L2 plugin can use. It adds support for some color palettes, and it is especially required by the spcaxxx driver you seem to be using. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From dsandras at seconix.com Tue Dec 30 20:29:18 2008 From: dsandras at seconix.com (Damien Sandras) Date: Tue, 30 Dec 2008 21:29:18 +0100 Subject: [Ekiga-list] Debian packages In-Reply-To: <495A790A.1010002@pu-pm.univ-fcomte.fr> References: <494E9244.4030701@pu-pm.univ-fcomte.fr> <20081221203342.GT5641@niof.net> <495A790A.1010002@pu-pm.univ-fcomte.fr> Message-ID: <1230668958.4514.10.camel@scorpion.multitel.be> Le mardi 30 d?cembre 2008 ? 20:39 +0100, Eugen Dedu a ?crit : > Rick Pasotto wrote: > > gnome-desktop-environment depends on ekiga (>= 2.0.12) > > > > Since 'aptitude install ekiga-snapshot' removes ekiga, > > gnome-desktop-environment becomes BROKEN and the installation > > would REMOVE 47 other packages. > > > > As far as I'm concerned, this means that ekiga-snapshot is NOT > > installable. > > > > I think that the problem is that the version number for ekiga-snapshot > > is 0-20081220-1 which is less than 2.0.12. Perhaps if the version number > > were changed to something greater that 2.0.12 (eg, 3-20081220-1) then > > the problem would go away. > > Hi, > > Increasing the version of ekiga-snapshot does not work. > > There are two solutions: > - either stay as we are now. Note that only gnome-desktop-environment > is removed (+old pwlwib/opal), not 47 packages!! > - or do not use ekiga-snapshot anymore, but ekiga (while ptlib and opal > are still named -snapshot, to avoid soname problems). Note that this > will not be intrusive or conflict with debian package, because the > version will be carefully chosen. > > What do people prefer?? > Perhaps 1:2008blah... would work ? -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From Eugen.Dedu at pu-pm.univ-fcomte.fr Tue Dec 30 20:30:22 2008 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Tue, 30 Dec 2008 21:30:22 +0100 Subject: [Ekiga-list] Debian packages In-Reply-To: <20081230201339.GO5641@niof.net> References: <494E9244.4030701@pu-pm.univ-fcomte.fr> <20081221203342.GT5641@niof.net> <495A790A.1010002@pu-pm.univ-fcomte.fr> <20081230201339.GO5641@niof.net> Message-ID: <495A84DE.6050400@pu-pm.univ-fcomte.fr> Rick Pasotto wrote: > On Tue, Dec 30, 2008 at 08:39:54PM +0100, Eugen Dedu wrote: >> Rick Pasotto wrote: >>> gnome-desktop-environment depends on ekiga (>= 2.0.12) >>> >>> Since 'aptitude install ekiga-snapshot' removes ekiga, >>> gnome-desktop-environment becomes BROKEN and the installation would >>> REMOVE 47 other packages. >>> >>> As far as I'm concerned, this means that ekiga-snapshot is NOT >>> installable. >>> >>> I think that the problem is that the version number for >>> ekiga-snapshot is 0-20081220-1 which is less than 2.0.12. Perhaps if >>> the version number were changed to something greater that 2.0.12 (eg, >>> 3-20081220-1) then the problem would go away. >> Hi, >> >> Increasing the version of ekiga-snapshot does not work. >> >> There are two solutions: - either stay as we are now. Note that only >> gnome-desktop-environment is removed (+old pwlwib/opal), not 47 >> packages!! - or do not use ekiga-snapshot anymore, but ekiga (while >> ptlib and opal are still named -snapshot, to avoid soname problems). >> Note that this will not be intrusive or conflict with debian package, >> because the version will be carefully chosen. >> >> What do people prefer?? > > Sorry to hear that changing the version number doesn't work. I'm not > really clear on exactly how the debian version number punctuation works. > Did you try using 3.0.0 or even 2.9? Perhaps the fact that the first > non-digit character is a '-' makes a difference. Provides does not yet work with version number. Here is a discussion on chat from this evening: hi! Pkg A in debian depends on pkg B (>= 2.0.12). I want to create pkg B-svn, which conflicts with B. Pkg B-svn has version 1.0. The question is: what can I do so that when users install B-svn, A still remains on the system? I have changed the version of B-svn to 3.0 and make it Provides and Conflicts and Replaces B, however it still does not work (I hope I am not wrong in my check). eugen-busy: why don't you give B version 2.0.12+svn-r1234 or something? eugen-busy: If you want to change the package name, you need to change A. The problem you are seeing is a misssing (?) feature in dpkg, usually called "versioned provides" I made it version 3.0, still does not work. Why 2.0.12+... should work? I cannot change A, A=gnome-desktop-environment eugen-busy: versioned-depends can't be resolved by provides. eugen-busy: Why not? gnome-desktop-environment is easy to change, even I can do so :) HE, is it a joke or serious? I don't see a joke statement here. * Piet has quit (Remote host closed the connection) so the correct solution is that I provide also gnome-desktop-environment with a modified Depends field? (only for pkg A)? eugen-busy: I'm more or less serious. It's not a problem to change g-d-e, it's just a package like every other (actually, it's even less complex, being a meta-package). And I can change it because I'm a Gnome maintainer :) it is not sufficient :o) I work on ekiga-snapshot packages. eugen-busy: Yeah, just change g-d-e to Depend on B (>= 2.0.12) | B-svn eugen-busy: versioned depends can't be resolved by provides. So if your B-svn must conflict with B and packages have versioned depends on B, these depending packages need to get changed. HE, could you change g-d-e to depend on ekiga (...) | ekiga-snapshot, provided that ekiga-snapshot is not in debian repository, but on ekiga own servers? do we really need two ekiga packages in the same suite? why not just upload the -svn version to experimental? it's because I change it very often, say once per week so? that's what we have version numbers for and what we have experimental for if it's really that volatile * glandium (~mh at 2a01:e35:8a5f:8130:21d:e0ff:fe26:f4b) has joined #debian-devel snapshots are not so stable, I think it's better to have them outside debian. eugen-busy: Errr ... Please file a bug ok, but you can still version them so they just naturally replace the earlier 'stable' snaphots HE, about what? e-snapshots for g-d-e or versioned provides? then you don't have to jump through name | name | name hoops, it all Just Works as it's supposed to ron, there is another impossible problem: ekiga depends on 2 libs, and these libs change the soname each month, so I cannot call them -snapshot too; and this pollutes package space (a binary package each month * 2) * jackyf has quit (Quit: KVIrc 3.4.0 Virgo http://www.kvirc.net/) * cortana (~sam at 62-31-63-21.cable.ubr12.aztw.blueyonder.co.uk) has joined #debian-devel eugen-busy: There's already a row of bugs about versioned provides, so just file one against g-d-e do they _release_ with a new soname each month, or are people just abusing it for intermediate snapshots at _every_ change? they _do_ release each month. I know it's not good, but... they _do_ release a new soname each month. I know it's not good, but... well then you are just going to build up a huge collection of libfoo{1,2,... 999} packages. that still doesn't mean you need a -snapshot package for either the libs or ekiga. just version them normally * mkrist has quit (Quit: leaving) I agree it's ugly, but there is no need to make it unnecessarily uglier. it's just like normal versioning and releases, just at 20x normal speed. it all still works the same fast or slow though -snapshot was the simplest for me... So you propose me to use the correct naming, such as libpt2.4.3 for the lib name, is that right? eugen-busy: you could always provide ekiga packages from your repo with the "ekiga" name hi paravoid! :) just name them so that dpkg --compare-versions always gets them in the right order then your ~svn snapshots replace older stable versions, and newer stable versions (when they come) will replace the ~svn ones from in-between s/name them/version them/ which is what you asked for initially, just much, much, simpler :) paravoid, how can I name them? The simplest was to have libpt-snapshot, libopal-snapshot, ekiga-snapshot and that's all. paravoid: btw. did you nag HE about getting the * fix into testing? (: To resume: the simplest think still seems to me to wait the versioned provides in g-d-e... (no need to change packages name). And all this in my own repo. * hanska__ (~hanska at host246-175-dynamic.2-79-r.retail.telecomitalia.it) has joined #debian-devel * hanska is now known as Guest77 * hanska__ is now known as hanska thanks to all and happy new year * Guest77 has quit (Ping timeout: 480 seconds) you don't even need to wait. if your versions increment as dpkg --compare-versions thinks they should, this will Just Work too ron, I still don't understand. I create ekiga-svn v. 3, and g-d-e depends on ekiga (>=2.0.12), and ekiga-svn conflicts with ekiga. This does not work! This does not work = when installing ekiga-svn, ekiga is removed and g-d-e too! right, so don't do that. instead just package ekiga 3.0~svn-whatever and let nature do the rest 3.0~svn _is_ >= 2.0.12 if my math doesn't entirely fail me and < 3.0 in the eyes of dpkg * tester (~tester at 78-83-87-170.spectrumnet.bg) has joined #debian-devel * tester has quit () eugen-busy: what ron said. just name them with a version that will allow it to upgraded but newer versions from Debian to supersede yours i.e. current Debian version (2.0.12-1) < your version < newer Debian version (e.g. 3.0-1) I am still thinking if it is ok... your version could be 2.1-1~snapshot1 or 3.0-1~snapshot1 etc. libopal and libpt will obviously have different names because of the upstream sillyness wrt sonames yes... Yes, I think it's ok. THANKS a lot, ron, it's the simplest solution. but that shouldn't affect you, since the whole thing with libary package naming is designed to allow coinstabillity Ok, THANKS a lot, ron; and paravoid. * m42 (~m42 at a81-84-75-214.cpe.netcabo.pt) has joined #debian-devel No need to fill a bug to g-d-e... > The number of packages that depend on gnome-desktop-environment will > vary from system to system. On my machine the following 45 packages > would be removed: > > arj{u} at-spi{u} cheese{u} dasher{u} dasher-data{u} dmz-cursor-theme{u} > eog{u} festival{u} festlex-cmu{u} festlex-poslex{u} festvox-kallpc16k{u} > file-roller{u} gcalctool{u} gconf-editor{u} gedit{u} gedit-common{u} > gnome-accessibility{u} gnome-accessibility-themes{u} gnome-core{u} > gnome-desktop-environment gnome-network-admin{u} gnome-orca{u} > gnome-power-manager{u} gnome-screensaver{u} gnome-themes{u} gok{u} > gstreamer0.10-tools{u} gucharmap{u} iceweasel-gnome-support{u} > libalut0{u} libavahi-ui0{u} libbrlapi0.5{u} libglew1.5{u} > libgnome-speech7{u} libgtk-vnc-1.0-0{u} libswfdec-0.6-90{u} libxevie1{u} > mousetweaks{u} python-brlapi{u} python-gtksourceview2{u} > python-pyatspi{u} rss-glx{u} swfdec-gnome{u} unace{u} vinagre{u} There's something wrong. Please check carefully that arj for ex. depends on g-d-e. Do you use apt-get remove (instead of dpkg -P) by chance?? This is a wrong (and dangerous) way to remove packages in my opinion. -- Eugen From Eugen.Dedu at pu-pm.univ-fcomte.fr Tue Dec 30 20:34:10 2008 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Tue, 30 Dec 2008 21:34:10 +0100 Subject: [Ekiga-list] Debian packages In-Reply-To: <1230668958.4514.10.camel@scorpion.multitel.be> References: <494E9244.4030701@pu-pm.univ-fcomte.fr> <20081221203342.GT5641@niof.net> <495A790A.1010002@pu-pm.univ-fcomte.fr> <1230668958.4514.10.camel@scorpion.multitel.be> Message-ID: <495A85C2.7010805@pu-pm.univ-fcomte.fr> Damien Sandras wrote: > Le mardi 30 d?cembre 2008 ? 20:39 +0100, Eugen Dedu a ?crit : >> Rick Pasotto wrote: >>> gnome-desktop-environment depends on ekiga (>= 2.0.12) >>> >>> Since 'aptitude install ekiga-snapshot' removes ekiga, >>> gnome-desktop-environment becomes BROKEN and the installation >>> would REMOVE 47 other packages. >>> >>> As far as I'm concerned, this means that ekiga-snapshot is NOT >>> installable. >>> >>> I think that the problem is that the version number for ekiga-snapshot >>> is 0-20081220-1 which is less than 2.0.12. Perhaps if the version number >>> were changed to something greater that 2.0.12 (eg, 3-20081220-1) then >>> the problem would go away. >> Hi, >> >> Increasing the version of ekiga-snapshot does not work. >> >> There are two solutions: >> - either stay as we are now. Note that only gnome-desktop-environment >> is removed (+old pwlwib/opal), not 47 packages!! >> - or do not use ekiga-snapshot anymore, but ekiga (while ptlib and opal >> are still named -snapshot, to avoid soname problems). Note that this >> will not be intrusive or conflict with debian package, because the >> version will be carefully chosen. >> >> What do people prefer?? >> > > Perhaps 1:2008blah... would work ? I tried 3-... and installed it. When I try to install g-d-e, it still wants to remove ekiga-snapshot and install ekiga etc. So here I was almost sure it does not work. I checked on debian guidelines or something like that, it says more or less that versioning does not work for provide, but it was not so clear to me. Finally, I was on chat and their answer is in my previous e-mail. -- Eugen From ml at stdout.at Tue Dec 30 20:39:34 2008 From: ml at stdout.at (Hannes Ebner) Date: Tue, 30 Dec 2008 21:39:34 +0100 Subject: [Ekiga-list] Debian packages In-Reply-To: <20081230201541.GP5641@niof.net> References: <494E9244.4030701@pu-pm.univ-fcomte.fr> <20081221203342.GT5641@niof.net> <495A790A.1010002@pu-pm.univ-fcomte.fr> <495A80BF.30001@stdout.at> <20081230201541.GP5641@niof.net> Message-ID: <495A8706.6090906@stdout.at> Rick Pasotto wrote: > Can the provides include a version number? I just read about it at , which says: So, a Provides field may not contain version numbers, and the version number of the concrete package which provides a particular virtual package will not be looked at when considering a dependency on or conflict with the virtual package name. That's also where the root of the problem lies, "gnome-desktop-environment" depends on a particular version number (or higher), which is not (and cannot be) provided by the virtual package. So it doesn't work via "provides". Sorry for the noise. Best regards, Hannes From Eugen.Dedu at pu-pm.univ-fcomte.fr Tue Dec 30 20:41:13 2008 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Tue, 30 Dec 2008 21:41:13 +0100 Subject: [Ekiga-list] G.722 or CELT in Ekiga? In-Reply-To: <1230662209.4514.3.camel@scorpion.multitel.be> References: <1230657702.9682.24.camel@mikael-xpsm1530> <1230662209.4514.3.camel@scorpion.multitel.be> Message-ID: <495A8769.2000400@pu-pm.univ-fcomte.fr> Damien Sandras wrote: > Hi, > > Le mardi 30 d?cembre 2008 ? 18:21 +0100, Mikael A. Bjerkeland a ?crit : >> Hi Damien, >> >> do you have any plans to add the G.722 and CELT >> (http://www.celt-codec.org/) codecs to Ekiga? > > > I just added G.722 support this week-end. > However, it is not interoperable (yet) with other implementations. Ekiga > advertises it as G722/16000 in the SDP (which is correct), but should > advertise it as G722/8000 (which is not correct, but everybody is doing > it that way because there is a mistake in the RFC!) > > I need to find the time to work on it. > > >> And what happened to the Debian builds? I can't find any of Ekiga 3. > > Not sure, they should be there. Eugen ? I have just uploaded them! They will be installable in 3 hours or so. Note that G722 is there too (but I didn't test it). -- Eugen From Eugen.Dedu at pu-pm.univ-fcomte.fr Tue Dec 30 20:43:24 2008 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Tue, 30 Dec 2008 21:43:24 +0100 Subject: [Ekiga-list] Debian packages In-Reply-To: <495A8706.6090906@stdout.at> References: <494E9244.4030701@pu-pm.univ-fcomte.fr> <20081221203342.GT5641@niof.net> <495A790A.1010002@pu-pm.univ-fcomte.fr> <495A80BF.30001@stdout.at> <20081230201541.GP5641@niof.net> <495A8706.6090906@stdout.at> Message-ID: <495A87EC.80002@pu-pm.univ-fcomte.fr> Hannes Ebner wrote: > Rick Pasotto wrote: >> Can the provides include a version number? > > I just read about it at > , > which says: > > So, a Provides field may not contain version numbers, and the version > number of the concrete package which provides a particular virtual > package will not be looked at when considering a dependency on or > conflict with the virtual package name. > > That's also where the root of the problem lies, > "gnome-desktop-environment" depends on a particular version number (or > higher), which is not (and cannot be) provided by the virtual package. Yes, but ekiga-snapshot is not a virtual package. That's why I was not sure 100%. > So it doesn't work via "provides". Sorry for the noise. -- Eugen From stefan at lucke.in-berlin.de Tue Dec 30 21:21:10 2008 From: stefan at lucke.in-berlin.de (Stefan Lucke) Date: Tue, 30 Dec 2008 22:21:10 +0100 Subject: [Ekiga-list] Colour format not supported with ekiga-svn In-Reply-To: <1230668888.4514.8.camel@scorpion.multitel.be> References: <200812301839.13422.stefan@lucke.in-berlin.de> <200812302002.25542.stefan@lucke.in-berlin.de> <1230668888.4514.8.camel@scorpion.multitel.be> Message-ID: <200812302221.10353.stefan@lucke.in-berlin.de> On Tuesday 30 December 2008, Damien Sandras wrote: > Le mardi 30 d?cembre 2008 ? 20:02 +0100, Stefan Lucke a ?crit : > > On Tuesday 30 December 2008, Damien Sandras wrote: > > > Hi, > > > > > > > > > Le mardi 30 d?cembre 2008 ? 18:39 +0100, Stefan Lucke a ?crit : > > > > Hi, > > > > > > > > I'm trying current svn version of ekiga & co (was a checkout from yesterday). > > > > My camera 'logitech quickcam connect' (046d:08d9) works quite well > > > > with ekiga 2.0.11, 2.0.12, 3.0.1 but unfortunately not with current svn. > > > > > > > > > > Did you compile PTLIB with libv4l support ? > > > > I think I did so: > > > > stefan at jarada /home/nfs/extra/src/video/Ekiga/Ekiga-2008-12-29/ptlib $ grep v4l config.log > > $ ./configure --prefix=/usr --enable-v4l --enable-v4l2 > > configure:16342: running /bin/sh ./configure '--prefix=/usr' '--enable-v4l' '--enable-v4l2' --cache-file=/dev/null --srcdir=. > > You are confusing 'building the V4L2' plugin and 'building the V4L2 > plugin with libv4l'. > > Libv4l is an external library that our V4L2 plugin can use. It adds > support for some color palettes, and it is especially required by the > spcaxxx driver you seem to be using. Thanks, I've been indeed a bit confused by those v4l options. But they where not necessary. A simple './configure --prefix=/usr' was enough for detecting everything after an 'emerge libv4l'. Ekiga svn version now works. -- Stefan Lucke From dsandras at seconix.com Tue Dec 30 21:27:30 2008 From: dsandras at seconix.com (Damien Sandras) Date: Tue, 30 Dec 2008 22:27:30 +0100 Subject: [Ekiga-list] Colour format not supported with ekiga-svn In-Reply-To: <200812302221.10353.stefan@lucke.in-berlin.de> References: <200812301839.13422.stefan@lucke.in-berlin.de> <200812302002.25542.stefan@lucke.in-berlin.de> <1230668888.4514.8.camel@scorpion.multitel.be> <200812302221.10353.stefan@lucke.in-berlin.de> Message-ID: <1230672450.4514.12.camel@scorpion.multitel.be> Le mardi 30 d?cembre 2008 ? 22:21 +0100, Stefan Lucke a ?crit : > On Tuesday 30 December 2008, Damien Sandras wrote: > > Le mardi 30 d?cembre 2008 ? 20:02 +0100, Stefan Lucke a ?crit : > > > On Tuesday 30 December 2008, Damien Sandras wrote: > > > > Hi, > > > > > > > > > > > > Le mardi 30 d?cembre 2008 ? 18:39 +0100, Stefan Lucke a ?crit : > > > > > Hi, > > > > > > > > > > I'm trying current svn version of ekiga & co (was a checkout from yesterday). > > > > > My camera 'logitech quickcam connect' (046d:08d9) works quite well > > > > > with ekiga 2.0.11, 2.0.12, 3.0.1 but unfortunately not with current svn. > > > > > > > > > > > > > Did you compile PTLIB with libv4l support ? > > > > > > I think I did so: > > > > > > stefan at jarada /home/nfs/extra/src/video/Ekiga/Ekiga-2008-12-29/ptlib $ grep v4l config.log > > > $ ./configure --prefix=/usr --enable-v4l --enable-v4l2 > > > configure:16342: running /bin/sh ./configure '--prefix=/usr' '--enable-v4l' '--enable-v4l2' --cache-file=/dev/null --srcdir=. > > > > You are confusing 'building the V4L2' plugin and 'building the V4L2 > > plugin with libv4l'. > > > > Libv4l is an external library that our V4L2 plugin can use. It adds > > support for some color palettes, and it is especially required by the > > spcaxxx driver you seem to be using. > > Thanks, I've been indeed a bit confused by those v4l options. But they > where not necessary. A simple './configure --prefix=/usr' was enough > for detecting everything after an 'emerge libv4l'. > Ekiga svn version now works. Excellent news! -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From fabrice at alphonso.dyndns.org Tue Dec 30 23:36:38 2008 From: fabrice at alphonso.dyndns.org (Fabrice ALPHONSO) Date: Wed, 31 Dec 2008 00:36:38 +0100 Subject: [Ekiga-list] Compile Problem In-Reply-To: <495A57B9.9050206@pu-pm.univ-fcomte.fr> References: <49556360.000002.20513@kamasutra> <4955853F.4090407@astronomicalresearchaustralia.org> <1230373752.24875.14.camel@scorpion.multitel.be> <49562D88.6090909@astronomicalresearchaustralia.org> <1230409601.30628.0.camel@scorpion.multitel.be> <49571AD4.1010703@astronomicalresearchaustralia.org> <1230487181.4343.0.camel@scorpion.multitel.be> <49582D6C.1040901@astronomicalresearchaustralia.org> <4958A742.9060808@pu-pm.univ-fcomte.fr> <4959FC19.2070404@astronomicalresearchaustralia.org> <495A57B9.9050206@pu-pm.univ-fcomte.fr> Message-ID: <1230680198.17744.4.camel@balder.walhalla> Hi guys, a quick mail to say I successfully compiled ekiga 3.0.1 on my OpenSUSE 11.1 (x86_64 version) at work past afternoon. just using the sources tarballs provided at www.ekiga.org I used standard ./configure command the only noticable thing is that I had to provide --libdir=/usr/lib64 explicitelly. I'll resend a mail tomorrow with the exact ./configure command I used when I'll be back at work. Hth, Fabrice Le mardi 30 d?cembre 2008 ? 18:17 +0100, Eugen Dedu a ?crit : > Brian wrote: > > Eugen, > > Thanks this put me on the right track. > > I can confirm that suse 11.1 is the problem. > > > > In ekiga-3.0.1/lib/engine/ it still uses *.la files all these have been > > removed in 11.1, in addition there is practically nothing in > > /opt/gnome/lib. Most of those files have been moved to /usr/lib. > > There were about 6 other files that were deleted altogether. > > What a mess! > > Anyway I got over all of them, and engine compiled ok. > > > > Now I get to > > /usr/lib/gcc/i586-suse-linux/4.3/../../../../i586-suse-linux/bin/ld: > > cannot find -lresmgr > > collect2: ld returned 1 exit status > > make[3]: *** [ekiga] Error 1 > > make[3]: Leaving directory `/Documents/SOURCE/SUSE11/ekiga-3.0.1/src' > > make[2]: *** [all] Error 2 > > make[2]: Leaving directory `/Documents/SOURCE/SUSE11/ekiga-3.0.1/src' > > make[1]: *** [all-recursive] Error 1 > > make[1]: Leaving directory `/Documents/SOURCE/SUSE11/ekiga-3.0.1' > > make: *** [all] Error 2 > > > > Only to discover that suse dropped support for resmgr after 10.3. > > It nolonger exists in 11.1. Suse now appears to use hal-resmgr. > > > > Once I figured out what libs were required where, I coped, but I do not > > understand how to proceed with this one. > > Is it possible to remove the requirement to load resmgr? > > Hi, > > I didn't know what resmgr is, so I took a look at > http://www.lst.de/~okir/resmgr. In debian, my machine, resmgr does not > exist. I searched resmgr in ekiga, ptlib and opal, and I haven't found > it either. So I imagine it's suse which adds it to the command line?? > Look at the parameters of gcc (gcc -v or other flags, I don't know). > Also, try to install the package providing resmgr library. > -- ALPHONSO Fabrice http://alphonso.dyndns.org/blog/ http://alphonso.dyndns.org/gallery2/ sip:fabrice at ekiga.net From bnc at astronomicalresearchaustralia.org Tue Dec 30 23:41:42 2008 From: bnc at astronomicalresearchaustralia.org (Brian) Date: Wed, 31 Dec 2008 09:41:42 +1000 Subject: [Ekiga-list] Compile Problem In-Reply-To: <495A57B9.9050206@pu-pm.univ-fcomte.fr> References: <49556360.000002.20513@kamasutra> <4955853F.4090407@astronomicalresearchaustralia.org> <1230373752.24875.14.camel@scorpion.multitel.be> <49562D88.6090909@astronomicalresearchaustralia.org> <1230409601.30628.0.camel@scorpion.multitel.be> <49571AD4.1010703@astronomicalresearchaustralia.org> <1230487181.4343.0.camel@scorpion.multitel.be> <49582D6C.1040901@astronomicalresearchaustralia.org> <4958A742.9060808@pu-pm.univ-fcomte.fr> <4959FC19.2070404@astronomicalresearchaustralia.org> <495A57B9.9050206@pu-pm.univ-fcomte.fr> Message-ID: <495AB1B6.8000303@astronomicalresearchaustralia.org> Eugen, >> Only to discover that suse dropped support for resmgr after 10.3. >> It nolonger exists in 11.1. Suse now appears to use hal-resmgr. >> >> Once I figured out what libs were required where, I coped, but I do not >> understand how to proceed with this one. >> Is it possible to remove the requirement to load resmgr? > > I didn't know what resmgr is, so I took a look at > http://www.lst.de/~okir/resmgr. In debian, my machine, resmgr does not > exist. I searched resmgr in ekiga, ptlib and opal, and I haven't found > it either. So I imagine it's suse which adds it to the command line?? > Look at the parameters of gcc (gcc -v or other flags, I don't know). > Also, try to install the package providing resmgr library. > On my system the following files reference resmgr. file:///Documents/SOURCE/SUSE11/ekiga-3.0.1/lib/engine/libekiga_engine.la file:///Documents/SOURCE/SUSE11/ekiga-3.0.1/lib/engine/.libs/libekiga_engine.la file:///Documents/SOURCE/SUSE11/ekiga-3.0.1/lib/libekiga.la file:///Documents/SOURCE/SUSE11/ekiga-3.0.1/lib/.libs/libekiga.la file:///Documents/SOURCE/SUSE11/ekiga-3.0.1/lib/engine/gui/gtk-core/libgmgtk-core.la file:///Documents/SOURCE/SUSE11/ekiga-3.0.1/lib/engine/gui/gtk-core/.libs/libgmgtk-core.la file:///Documents/SOURCE/SUSE11/ekiga-3.0.1/lib/engine/gui/gtk-frontend/libgmgtk-frontend.la file:///Documents/SOURCE/SUSE11/ekiga-3.0.1/lib/engine/gui/gtk-frontend/.libs/libgmgtk-frontend.la file:///Documents/SOURCE/SUSE11/ekiga-3.0.1/lib/gui/libgmwidgets.la file:///Documents/SOURCE/SUSE11/ekiga-3.0.1/lib/gui/.libs/libgmwidgets.la file:///Documents/SOURCE/SUSE11/ekiga-3.0.1/lib/toolbox/libtoolbox.la file:///Documents/SOURCE/SUSE11/ekiga-3.0.1/lib/toolbox/.libs/libtoolbox.la On your debian system do you use *.la files at all? If not then I need to look at why I do. Thanks, Brian From bnc at astronomicalresearchaustralia.org Tue Dec 30 23:58:58 2008 From: bnc at astronomicalresearchaustralia.org (Brian) Date: Wed, 31 Dec 2008 09:58:58 +1000 Subject: [Ekiga-list] Compile Problem In-Reply-To: <1230680198.17744.4.camel@balder.walhalla> References: <49556360.000002.20513@kamasutra> <4955853F.4090407@astronomicalresearchaustralia.org> <1230373752.24875.14.camel@scorpion.multitel.be> <49562D88.6090909@astronomicalresearchaustralia.org> <1230409601.30628.0.camel@scorpion.multitel.be> <49571AD4.1010703@astronomicalresearchaustralia.org> <1230487181.4343.0.camel@scorpion.multitel.be> <49582D6C.1040901@astronomicalresearchaustralia.org> <4958A742.9060808@pu-pm.univ-fcomte.fr> <4959FC19.2070404@astronomicalresearchaustralia.org> <495A57B9.9050206@pu-pm.univ-fcomte.fr> <1230680198.17744.4.camel@balder.walhalla> Message-ID: <495AB5C2.9030308@astronomicalresearchaustralia.org> Fabrice, > > a quick mail to say I successfully compiled ekiga 3.0.1 on my OpenSUSE > > 11.1 (x86_64 version) at work past afternoon. > > just using the sources tarballs provided at www.ekiga.org > > I used standard ./configure command the only noticable thing is that I > > had to provide --libdir=/usr/lib64 explicitelly. > > Great, at least we know it is possible. Can I ask if you did a new install of 11.1 or an upgrade? I am using the same tarballs as you but somehow I end up looking for resmgr. > > I'll resend a mail tomorrow with the exact ./configure command I used > > when I'll be back at work. > > Will give it another go as soon as I get it. Brian From fabrice at alphonso.dyndns.org Wed Dec 31 08:44:24 2008 From: fabrice at alphonso.dyndns.org (ALPHONSO Fabrice) Date: Wed, 31 Dec 2008 09:44:24 +0100 (CET) Subject: [Ekiga-list] Compile Problem In-Reply-To: <495AB5C2.9030308@astronomicalresearchaustralia.org> References: <49556360.000002.20513@kamasutra> <4955853F.4090407@astronomicalresearchaustralia.org> <1230373752.24875.14.camel@scorpion.multitel.be> <49562D88.6090909@astronomicalresearchaustralia.org> <1230409601.30628.0.camel@scorpion.multitel.be> <49571AD4.1010703@astronomicalresearchaustralia.org> <1230487181.4343.0.camel@scorpion.multitel.be> <49582D6C.1040901@astronomicalresearchaustralia.org> <4958A742.9060808@pu-pm.univ-fcomte.fr> <4959FC19.2070404@astronomicalresearchaustralia.org> <495A57B9.9050206@pu-pm.univ-fcomte.fr> <1230680198.17744.4.camel@balder.walhalla> <495AB5C2.9030308@astronomicalresearchaustralia.org> Message-ID: <18426.83.206.226.2.1230713064.squirrel@alphonso.dyndns.org> On Wed, December 31, 2008 12:58 am, Brian wrote: > Fabrice, >> > a quick mail to say I successfully compiled ekiga 3.0.1 on my OpenSUSE >> > 11.1 (x86_64 version) at work past afternoon. >> > just using the sources tarballs provided at www.ekiga.org >> > I used standard ./configure command the only noticable thing is that >> I >> > had to provide --libdir=/usr/lib64 explicitelly. >> > > Great, at least we know it is possible. > Can I ask if you did a new install of 11.1 or an upgrade? > I am using the same tarballs as you but somehow I end up looking for > resmgr. It was indeed an upgrade from a 11.0 upgraded from a 10.X version... But a search with zypper cli or even yast2's package manager doesn't show me anything about "resmgr"... > >> > I'll resend a mail tomorrow with the exact ./configure command I used >> > when I'll be back at work. >> > > Will give it another go as soon as I get it. Here are the ./configure commands I used : To compile ptlib : ./configure --enable-audio --enable-video --disable-avc --disable-dc --enable-alsa --disable-oss --enable-v4l2 --enable-v4l --enable-plugins --enable-opal --prefix=/usr --sysconfdir=/etc --libdir=/usr/lib64 To compile opal : ./configure --prefix=/usr --sysconfdir=/etc --libdir=/usr/lib64 --enable-plugins --enable-video --enable-localspeex To compile ekiga : ./configure --prefix=/usr --sysconfdir=/etc --libdir=/usr/lib64 I know it's not usual OpenSUSE pathes, official packages certainly put things in some other pathes, but it seems to work as is for me as just after installing, it started fine and I had a successfull connection with another Ekiga 3.0.2beta for Windows installed on another PC in my LAN. > > Brian Hth, Fabrice From stefan at lucke.in-berlin.de Wed Dec 31 08:48:54 2008 From: stefan at lucke.in-berlin.de (Stefan Lucke) Date: Wed, 31 Dec 2008 09:48:54 +0100 Subject: [Ekiga-list] Error message when exiting ekiga. Message-ID: <200812310948.54656.stefan@lucke.in-berlin.de> Hi, I get the following error message upon exiting ekiga: stefan at jarada ~ $ date;ekiga;date Mi 31. Dez 09:46:28 CET 2008 assert.cxx(108) PWLib Assertion fail: Function pthread_mutex_lock failed, file ptlib/unix/tlibthrd.cxx, line 1304 Assertion fail: Function pthread_mutex_lock failed, file ptlib/unix/tlibthrd.cxx, line 1304 bort, ore dump? A Aborting. Mi 31. Dez 09:46:41 CET 2008 I'm using svn checkout of ekiga from 2008-12-29. Should I provide a dump or some other debug information or report this problem elsewhere? -- Stefan Lucke From dsandras at seconix.com Wed Dec 31 09:31:32 2008 From: dsandras at seconix.com (Damien Sandras) Date: Wed, 31 Dec 2008 10:31:32 +0100 Subject: [Ekiga-list] Error message when exiting ekiga. In-Reply-To: <200812310948.54656.stefan@lucke.in-berlin.de> References: <200812310948.54656.stefan@lucke.in-berlin.de> Message-ID: <1230715892.20800.11.camel@scorpion.multitel.be> Le mercredi 31 d?cembre 2008 ? 09:48 +0100, Stefan Lucke a ?crit : > Hi, > > I get the following error message upon exiting ekiga: > > stefan at jarada ~ $ date;ekiga;date > Mi 31. Dez 09:46:28 CET 2008 > assert.cxx(108) PWLib Assertion fail: Function pthread_mutex_lock failed, file ptlib/unix/tlibthrd.cxx, line 1304 > Assertion fail: Function pthread_mutex_lock failed, file ptlib/unix/tlibthrd.cxx, line 1304 > > bort, ore dump? A > > Aborting. > Mi 31. Dez 09:46:41 CET 2008 > > I'm using svn checkout of ekiga from 2008-12-29. > Should I provide a dump or some other debug information or report this problem elsewhere? A full GDB backtrace (see the wiki for more details on http://wiki.ekiga.org). -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From stefan at lucke.in-berlin.de Wed Dec 31 10:45:03 2008 From: stefan at lucke.in-berlin.de (Stefan Lucke) Date: Wed, 31 Dec 2008 11:45:03 +0100 Subject: [Ekiga-list] Error message when exiting ekiga. In-Reply-To: <1230715892.20800.11.camel@scorpion.multitel.be> References: <200812310948.54656.stefan@lucke.in-berlin.de> <1230715892.20800.11.camel@scorpion.multitel.be> Message-ID: <200812311145.03140.stefan@lucke.in-berlin.de> On Wednesday 31 December 2008, Damien Sandras wrote: > Le mercredi 31 d?cembre 2008 ? 09:48 +0100, Stefan Lucke a ?crit : > > Hi, > > > > I get the following error message upon exiting ekiga: > > > > stefan at jarada ~ $ date;ekiga;date > > Mi 31. Dez 09:46:28 CET 2008 > > assert.cxx(108) PWLib Assertion fail: Function pthread_mutex_lock failed, file ptlib/unix/tlibthrd.cxx, line 1304 > > Assertion fail: Function pthread_mutex_lock failed, file ptlib/unix/tlibthrd.cxx, line 1304 > > > > bort, ore dump? A > > > > Aborting. > > Mi 31. Dez 09:46:41 CET 2008 > > > > I'm using svn checkout of ekiga from 2008-12-29. > > Should I provide a dump or some other debug information or report this problem elsewhere? > > > A full GDB backtrace (see the wiki for more details on > http://wiki.ekiga.org). ptlib cannot be build with: 'make DEBUG=1 debug' and thus opal cannot be confgured with --enable-debug when ptlib is build without DEBUG=1. cxx -o /home/nfs/extra/src/video/Ekiga/Ekiga-2008-12-29/ptlib/lib_linux_x86/obj_d/tinyjpeg.o g++ -DPTRACING=1 -D_REENTRANT -D_GNU_SOURCE=1 -D_REENTRANT -I/usr/include/SDL -fno-exceptions -Wall -fPIC -DPIC -g3 -ggdb -O0 -D_DEBUG -I/home/nfs/extra/src/video/Ekiga/Ekiga-2008-12-29/ptlib/include -felide-constructors -Wreorder -c ptlib/common/jidctflt.cxx -o /home/nfs/extra/src/video/Ekiga/Ekiga-2008-12-29/ptlib/lib_linux_x86/obj_d/jidctflt.o /tmp/ccJhh47h.s: Assembler messages: /tmp/ccJhh47h.s:1101: Error: suffix or operands invalid for `sar' make[2]: *** [/home/nfs/extra/src/video/Ekiga/Ekiga-2008-12-29/ptlib/lib_linux_x86/obj_d/jidctflt.o] Fehler 1 make[2]: Leaving directory `/home/nfs/extra/src/video/Ekiga/Ekiga-2008-12-29/ptlib/src' make[1]: *** [debug] Fehler 2 make[1]: Leaving directory `/home/nfs/extra/src/video/Ekiga/Ekiga-2008-12-29/ptlib/src' make: *** [debug] Fehler 2 So that's most info what I can get for now (running ekiga from gdb): (gdb) run Starting program: /usr/bin/ekiga [Thread debugging using libthread_db enabled] [New Thread 0xb5fda6d0 (LWP 14886)] [New Thread 0xb52d8b90 (LWP 14892)] [New Thread 0xb5297b90 (LWP 14893)] [New Thread 0xb5256b90 (LWP 14894)] [New Thread 0xb5215b90 (LWP 14895)] [New Thread 0xb51d4b90 (LWP 14896)] [New Thread 0xb5193b90 (LWP 14897)] [New Thread 0xb5152b90 (LWP 14898)] [New Thread 0xb4fffb90 (LWP 14899)] [New Thread 0xb4fbeb90 (LWP 14900)] [New Thread 0xb4f7db90 (LWP 14901)] [New Thread 0xb477cb90 (LWP 14911)] [Thread 0xb4fbeb90 (LWP 14900) exited] [New Thread 0xaf7b6b90 (LWP 14919)] [Thread 0xaf7b6b90 (LWP 14919) exited] [Thread 0xb4fffb90 (LWP 14899) exited] [New Thread 0xb4fffb90 (LWP 14921)] [Thread 0xb5152b90 (LWP 14898) exited] [New Thread 0xb5152b90 (LWP 14922)] [New Thread 0xb4fbeb90 (LWP 14923)] [Thread 0xb4fbeb90 (LWP 14923) exited] [Thread 0xb5256b90 (LWP 14894) exited] assert.cxx(108) PWLib Assertion fail: Function pthread_mutex_lock failed, file ptlib/unix/tlibthrd.cxx, line 1304 Assertion fail: Function pthread_mutex_lock failed, file ptlib/unix/tlibthrd.cxx, line 1304 bort, ore dump? C Dumping core. Ignoring. assert.cxx(108) PWLib Assertion fail: Function pthread_mutex_unlock failed, file ptlib/unix/tlibthrd.cxx, line 1405 Assertion fail: Function pthread_mutex_unlock failed, file ptlib/unix/tlibthrd.cxx, line 1405 bort, ore dump? bort, ore dump? Program received signal SIGABRT, Aborted. [Switching to Thread 0xb5fda6d0 (LWP 14886)] 0xffffe424 in __kernel_vsyscall () (gdb) bt full #0 0xffffe424 in __kernel_vsyscall () No symbol table info available. #1 0xb6cd0576 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 No symbol table info available. #2 0xb70f1301 in PSyncPoint::Wait () from /usr/lib/libpt.so.2.5-beta2 No symbol table info available. #3 0x081cbccb in Ekiga::VideoInputCore::VideoPreviewManager::stop (this=0x834579c) at ../../../../lib/engine/videoinput/skel/videoinput-core.cpp:89 No locals. #4 0x081cbe8c in ~VideoPreviewManager (this=0x834579c) at ../../../../lib/engine/videoinput/skel/videoinput-core.cpp:66 No locals. #5 0x081cfd51 in ~VideoInputCore (this=0x83456a0) at ../../../../lib/engine/videoinput/skel/videoinput-core.cpp:166 No locals. #6 0x08143248 in gmref_ptr::reset (this=0x8346150) at ../../../../lib/engine/framework/gmref.h:108 No locals. #7 0x081b6666 in ~ServiceCore (this=0x8348a40) at /usr/lib/gcc/i686-pc-linux-gnu/4.1.2/include/g++-v4/ext/new_allocator.h:109 No locals. #8 0x0817b0a9 in engine_stop () at engine.cpp:318 No locals. #9 0x0816d0a6 in GnomeMeeting::StopEngine (this=0x8303020) at ekiga.cpp:238 No locals. #10 0x08154dfb in main (argc=0, argv=0x0) at gui/main.cpp:4561 context = main_window = (GtkWidget *) 0x84379e8 assistant_window = url = (gchar *) 0x0 debug_level = 0 debug_level_up = 0 arguments = {{long_name = 0x82b1190 "debug", short_name = 100 'd', flags = 0, arg = G_OPTION_ARG_INT, arg_data = 0xbfbf59e0, description = 0x82b0968 "Prints debug messages in the console (level between 1 and 5)", arg_description = 0x0}, {long_name = 0x82b1196 "debug_user_plane", short_name = 117 'u', flags = 0, arg = G_OPTION_ARG_INT, arg_data = 0xbfbf59dc, description = 0x82b09a8 "Prints user plane debug messages in the console (level between 1 and 4)", arg_description = 0x0}, {long_name = 0x82cbcf0 "call", short_name = 99 'c', flags = 0, arg = G_OPTION_ARG_STRING, arg_data = 0xbfbf59e4, description = 0x82b09f0 "Makes Ekiga call the given URI", arg_description = 0x0}, { long_name = 0x0, short_name = 0 '\0', flags = 0, arg = G_OPTION_ARG_NONE, arg_data = 0x0, description = 0x0, arg_description = 0x0}} mw = (EkigaMainWindow *) 0x84379e8 call_core = {obj = 0x8345500} dbus_component = (EkigaDBusComponent *) 0x84ff600 instance = {<> = {}, ep_var_mutex = , dev_access_mutex = , call_number = 0, main_window = 0x0, history_window = 0x0, assistant_window = 0x0, prefs_window = 0x0, accounts_window = 0x0, statusicon = 0x0, dbus_component = 0x0, static GM = 0x8303020} (gdb) -- Stefan Lucke From Eugen.Dedu at pu-pm.univ-fcomte.fr Wed Dec 31 10:49:00 2008 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Wed, 31 Dec 2008 11:49:00 +0100 Subject: [Ekiga-list] Compile Problem In-Reply-To: <495AB1B6.8000303@astronomicalresearchaustralia.org> References: <49556360.000002.20513@kamasutra> <4955853F.4090407@astronomicalresearchaustralia.org> <1230373752.24875.14.camel@scorpion.multitel.be> <49562D88.6090909@astronomicalresearchaustralia.org> <1230409601.30628.0.camel@scorpion.multitel.be> <49571AD4.1010703@astronomicalresearchaustralia.org> <1230487181.4343.0.camel@scorpion.multitel.be> <49582D6C.1040901@astronomicalresearchaustralia.org> <4958A742.9060808@pu-pm.univ-fcomte.fr> <4959FC19.2070404@astronomicalresearchaustralia.org> <495A57B9.9050206@pu-pm.univ-fcomte.fr> <495AB1B6.8000303@astronomicalresearchaustralia.org> Message-ID: <495B4E1C.90203@pu-pm.univ-fcomte.fr> Brian wrote: > > Eugen, >>> Only to discover that suse dropped support for resmgr after 10.3. >>> It nolonger exists in 11.1. Suse now appears to use hal-resmgr. >>> >>> Once I figured out what libs were required where, I coped, but I do not >>> understand how to proceed with this one. >>> Is it possible to remove the requirement to load resmgr? >> I didn't know what resmgr is, so I took a look at >> http://www.lst.de/~okir/resmgr. In debian, my machine, resmgr does not >> exist. I searched resmgr in ekiga, ptlib and opal, and I haven't found >> it either. So I imagine it's suse which adds it to the command line?? >> Look at the parameters of gcc (gcc -v or other flags, I don't know). >> Also, try to install the package providing resmgr library. >> > On my system the following files reference resmgr. > file:///Documents/SOURCE/SUSE11/ekiga-3.0.1/lib/engine/libekiga_engine.la > file:///Documents/SOURCE/SUSE11/ekiga-3.0.1/lib/engine/.libs/libekiga_engine.la > file:///Documents/SOURCE/SUSE11/ekiga-3.0.1/lib/libekiga.la > file:///Documents/SOURCE/SUSE11/ekiga-3.0.1/lib/.libs/libekiga.la > file:///Documents/SOURCE/SUSE11/ekiga-3.0.1/lib/engine/gui/gtk-core/libgmgtk-core.la > file:///Documents/SOURCE/SUSE11/ekiga-3.0.1/lib/engine/gui/gtk-core/.libs/libgmgtk-core.la > file:///Documents/SOURCE/SUSE11/ekiga-3.0.1/lib/engine/gui/gtk-frontend/libgmgtk-frontend.la > file:///Documents/SOURCE/SUSE11/ekiga-3.0.1/lib/engine/gui/gtk-frontend/.libs/libgmgtk-frontend.la > file:///Documents/SOURCE/SUSE11/ekiga-3.0.1/lib/gui/libgmwidgets.la > file:///Documents/SOURCE/SUSE11/ekiga-3.0.1/lib/gui/.libs/libgmwidgets.la > file:///Documents/SOURCE/SUSE11/ekiga-3.0.1/lib/toolbox/libtoolbox.la > file:///Documents/SOURCE/SUSE11/ekiga-3.0.1/lib/toolbox/.libs/libtoolbox.la > > On your debian system do you use *.la files at all? > If not then I need to look at why I do. In the original version (sources only), I do not have these files. After compilation, I do have these files, but they do not reference resmgr. -- Eugen From Eugen.Dedu at pu-pm.univ-fcomte.fr Wed Dec 31 10:57:42 2008 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Wed, 31 Dec 2008 11:57:42 +0100 Subject: [Ekiga-list] Error message when exiting ekiga. In-Reply-To: <200812311145.03140.stefan@lucke.in-berlin.de> References: <200812310948.54656.stefan@lucke.in-berlin.de> <1230715892.20800.11.camel@scorpion.multitel.be> <200812311145.03140.stefan@lucke.in-berlin.de> Message-ID: <495B5026.2020601@pu-pm.univ-fcomte.fr> Stefan Lucke wrote: > On Wednesday 31 December 2008, Damien Sandras wrote: >> Le mercredi 31 d?cembre 2008 ? 09:48 +0100, Stefan Lucke a ?crit : >>> Hi, >>> >>> I get the following error message upon exiting ekiga: >>> >>> stefan at jarada ~ $ date;ekiga;date >>> Mi 31. Dez 09:46:28 CET 2008 >>> assert.cxx(108) PWLib Assertion fail: Function pthread_mutex_lock failed, file ptlib/unix/tlibthrd.cxx, line 1304 >>> Assertion fail: Function pthread_mutex_lock failed, file ptlib/unix/tlibthrd.cxx, line 1304 >>> >>> bort, ore dump? A >>> >>> Aborting. >>> Mi 31. Dez 09:46:41 CET 2008 >>> >>> I'm using svn checkout of ekiga from 2008-12-29. >>> Should I provide a dump or some other debug information or report this problem elsewhere? >> >> A full GDB backtrace (see the wiki for more details on >> http://wiki.ekiga.org). > > ptlib cannot be build with: 'make DEBUG=1 debug' and thus opal cannot > be confgured with --enable-debug when ptlib is build without DEBUG=1. > > cxx -o /home/nfs/extra/src/video/Ekiga/Ekiga-2008-12-29/ptlib/lib_linux_x86/obj_d/tinyjpeg.o > g++ -DPTRACING=1 -D_REENTRANT -D_GNU_SOURCE=1 -D_REENTRANT -I/usr/include/SDL -fno-exceptions -Wall -fPIC -DPIC -g3 -ggdb -O0 -D_DEBUG -I/home/nfs/extra/src/video/Ekiga/Ekiga-2008-12-29/ptlib/include -felide-constructors -Wreorder -c ptlib/common/jidctflt.cxx -o /home/nfs/extra/src/video/Ekiga/Ekiga-2008-12-29/ptlib/lib_linux_x86/obj_d/jidctflt.o > /tmp/ccJhh47h.s: Assembler messages: > /tmp/ccJhh47h.s:1101: Error: suffix or operands invalid for `sar' > make[2]: *** [/home/nfs/extra/src/video/Ekiga/Ekiga-2008-12-29/ptlib/lib_linux_x86/obj_d/jidctflt.o] Fehler 1 > make[2]: Leaving directory `/home/nfs/extra/src/video/Ekiga/Ekiga-2008-12-29/ptlib/src' > make[1]: *** [debug] Fehler 2 > make[1]: Leaving directory `/home/nfs/extra/src/video/Ekiga/Ekiga-2008-12-29/ptlib/src' > make: *** [debug] Fehler 2 Hi, Do you use gcc or other compiler? What version? Are you on a 64-bit machine? Intel or AMD? It seems to me that your uP does not know the assembler code in jidctflt.cxx:110. As a workaround, you can put the 'else' branch in the 'then' too. -- Eugen From Eugen.Dedu at pu-pm.univ-fcomte.fr Wed Dec 31 10:59:35 2008 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Wed, 31 Dec 2008 11:59:35 +0100 Subject: [Ekiga-list] Error message when exiting ekiga. In-Reply-To: <200812311145.03140.stefan@lucke.in-berlin.de> References: <200812310948.54656.stefan@lucke.in-berlin.de> <1230715892.20800.11.camel@scorpion.multitel.be> <200812311145.03140.stefan@lucke.in-berlin.de> Message-ID: <495B5097.10000@pu-pm.univ-fcomte.fr> Stefan Lucke wrote: > On Wednesday 31 December 2008, Damien Sandras wrote: >> Le mercredi 31 d?cembre 2008 ? 09:48 +0100, Stefan Lucke a ?crit : >>> Hi, >>> >>> I get the following error message upon exiting ekiga: >>> >>> stefan at jarada ~ $ date;ekiga;date >>> Mi 31. Dez 09:46:28 CET 2008 >>> assert.cxx(108) PWLib Assertion fail: Function pthread_mutex_lock failed, file ptlib/unix/tlibthrd.cxx, line 1304 >>> Assertion fail: Function pthread_mutex_lock failed, file ptlib/unix/tlibthrd.cxx, line 1304 >>> >>> bort, ore dump? A >>> >>> Aborting. >>> Mi 31. Dez 09:46:41 CET 2008 >>> >>> I'm using svn checkout of ekiga from 2008-12-29. >>> Should I provide a dump or some other debug information or report this problem elsewhere? >> >> A full GDB backtrace (see the wiki for more details on >> http://wiki.ekiga.org). > > ptlib cannot be build with: 'make DEBUG=1 debug' and thus opal cannot > be confgured with --enable-debug when ptlib is build without DEBUG=1. > > cxx -o /home/nfs/extra/src/video/Ekiga/Ekiga-2008-12-29/ptlib/lib_linux_x86/obj_d/tinyjpeg.o > g++ -DPTRACING=1 -D_REENTRANT -D_GNU_SOURCE=1 -D_REENTRANT -I/usr/include/SDL -fno-exceptions -Wall -fPIC -DPIC -g3 -ggdb -O0 -D_DEBUG -I/home/nfs/extra/src/video/Ekiga/Ekiga-2008-12-29/ptlib/include -felide-constructors -Wreorder -c ptlib/common/jidctflt.cxx -o /home/nfs/extra/src/video/Ekiga/Ekiga-2008-12-29/ptlib/lib_linux_x86/obj_d/jidctflt.o > /tmp/ccJhh47h.s: Assembler messages: > /tmp/ccJhh47h.s:1101: Error: suffix or operands invalid for `sar' > make[2]: *** [/home/nfs/extra/src/video/Ekiga/Ekiga-2008-12-29/ptlib/lib_linux_x86/obj_d/jidctflt.o] Fehler 1 > make[2]: Leaving directory `/home/nfs/extra/src/video/Ekiga/Ekiga-2008-12-29/ptlib/src' > make[1]: *** [debug] Fehler 2 > make[1]: Leaving directory `/home/nfs/extra/src/video/Ekiga/Ekiga-2008-12-29/ptlib/src' > make: *** [debug] Fehler 2 Could you also send include/ptbuildopts.h? -- Eugen From stefan at lucke.in-berlin.de Wed Dec 31 11:38:48 2008 From: stefan at lucke.in-berlin.de (Stefan Lucke) Date: Wed, 31 Dec 2008 12:38:48 +0100 Subject: [Ekiga-list] Error message when exiting ekiga. In-Reply-To: <495B5026.2020601@pu-pm.univ-fcomte.fr> References: <200812310948.54656.stefan@lucke.in-berlin.de> <200812311145.03140.stefan@lucke.in-berlin.de> <495B5026.2020601@pu-pm.univ-fcomte.fr> Message-ID: <200812311238.48760.stefan@lucke.in-berlin.de> On Wednesday 31 December 2008, Eugen Dedu wrote: > Stefan Lucke wrote: > > On Wednesday 31 December 2008, Damien Sandras wrote: > >> Le mercredi 31 d?cembre 2008 ? 09:48 +0100, Stefan Lucke a ?crit : > >>> Hi, > >>> > >>> I get the following error message upon exiting ekiga: > >>> > >>> stefan at jarada ~ $ date;ekiga;date > >>> Mi 31. Dez 09:46:28 CET 2008 > >>> assert.cxx(108) PWLib Assertion fail: Function pthread_mutex_lock failed, file ptlib/unix/tlibthrd.cxx, line 1304 > >>> Assertion fail: Function pthread_mutex_lock failed, file ptlib/unix/tlibthrd.cxx, line 1304 > >>> > >>> bort, ore dump? A > >>> > >>> Aborting. > >>> Mi 31. Dez 09:46:41 CET 2008 > >>> > >>> I'm using svn checkout of ekiga from 2008-12-29. > >>> Should I provide a dump or some other debug information or report this problem elsewhere? > >> > >> A full GDB backtrace (see the wiki for more details on > >> http://wiki.ekiga.org). > > > > ptlib cannot be build with: 'make DEBUG=1 debug' and thus opal cannot > > be confgured with --enable-debug when ptlib is build without DEBUG=1. > > > > cxx -o /home/nfs/extra/src/video/Ekiga/Ekiga-2008-12-29/ptlib/lib_linux_x86/obj_d/tinyjpeg.o > > g++ -DPTRACING=1 -D_REENTRANT -D_GNU_SOURCE=1 -D_REENTRANT -I/usr/include/SDL -fno-exceptions -Wall -fPIC -DPIC -g3 -ggdb -O0 -D_DEBUG -I/home/nfs/extra/src/video/Ekiga/Ekiga-2008-12-29/ptlib/include -felide-constructors -Wreorder -c ptlib/common/jidctflt.cxx -o /home/nfs/extra/src/video/Ekiga/Ekiga-2008-12-29/ptlib/lib_linux_x86/obj_d/jidctflt.o > > /tmp/ccJhh47h.s: Assembler messages: > > /tmp/ccJhh47h.s:1101: Error: suffix or operands invalid for `sar' > > make[2]: *** [/home/nfs/extra/src/video/Ekiga/Ekiga-2008-12-29/ptlib/lib_linux_x86/obj_d/jidctflt.o] Fehler 1 > > make[2]: Leaving directory `/home/nfs/extra/src/video/Ekiga/Ekiga-2008-12-29/ptlib/src' > > make[1]: *** [debug] Fehler 2 > > make[1]: Leaving directory `/home/nfs/extra/src/video/Ekiga/Ekiga-2008-12-29/ptlib/src' > > make: *** [debug] Fehler 2 > > Hi, > > Do you use gcc or other compiler? What version? Are you on a 64-bit > machine? Intel or AMD? gcc (GCC) 4.1.2 (Gentoo 4.1.2 p1.1) Copyright (C) 2006 Free Software Foundation, Inc. Processor is: AMD Athlon(tm) 64 X2 Dual Core Processor 5600+ The system is NOT generated as 64 bit system. Attached file 'include/ptbuildopts.h', bzip2 compressed. > > It seems to me that your uP does not know the assembler code in > jidctflt.cxx:110. As a workaround, you can put the 'else' branch in the > 'then' too. Thanks, will do/try that later. -- Stefan Lucke -------------- next part -------------- A non-text attachment was scrubbed... Name: ptbuildopts.h.bz2 Type: application/x-bzip2 Size: 3884 bytes Desc: not available URL: From stefan at lucke.in-berlin.de Wed Dec 31 13:24:18 2008 From: stefan at lucke.in-berlin.de (Stefan Lucke) Date: Wed, 31 Dec 2008 14:24:18 +0100 Subject: [Ekiga-list] Error message when exiting ekiga. In-Reply-To: <495B5026.2020601@pu-pm.univ-fcomte.fr> References: <200812310948.54656.stefan@lucke.in-berlin.de> <200812311145.03140.stefan@lucke.in-berlin.de> <495B5026.2020601@pu-pm.univ-fcomte.fr> Message-ID: <200812311424.18784.stefan@lucke.in-berlin.de> On Wednesday 31 December 2008, Eugen Dedu wrote: > Stefan Lucke wrote: > > On Wednesday 31 December 2008, Damien Sandras wrote: > >> Le mercredi 31 d?cembre 2008 ? 09:48 +0100, Stefan Lucke a ?crit : > >>> Hi, > >>> > >>> I get the following error message upon exiting ekiga: > >>> > >>> stefan at jarada ~ $ date;ekiga;date > >>> Mi 31. Dez 09:46:28 CET 2008 > >>> assert.cxx(108) PWLib Assertion fail: Function pthread_mutex_lock failed, file ptlib/unix/tlibthrd.cxx, line 1304 > >>> Assertion fail: Function pthread_mutex_lock failed, file ptlib/unix/tlibthrd.cxx, line 1304 > >>> > >>> bort, ore dump? A > >>> > >>> Aborting. > >>> Mi 31. Dez 09:46:41 CET 2008 > >>> > >>> I'm using svn checkout of ekiga from 2008-12-29. > >>> Should I provide a dump or some other debug information or report this problem elsewhere? > >> > >> A full GDB backtrace (see the wiki for more details on > >> http://wiki.ekiga.org). > > > > ptlib cannot be build with: 'make DEBUG=1 debug' and thus opal cannot > > be confgured with --enable-debug when ptlib is build without DEBUG=1. > > > > cxx -o /home/nfs/extra/src/video/Ekiga/Ekiga-2008-12-29/ptlib/lib_linux_x86/obj_d/tinyjpeg.o > > g++ -DPTRACING=1 -D_REENTRANT -D_GNU_SOURCE=1 -D_REENTRANT -I/usr/include/SDL -fno-exceptions -Wall -fPIC -DPIC -g3 -ggdb -O0 -D_DEBUG -I/home/nfs/extra/src/video/Ekiga/Ekiga-2008-12-29/ptlib/include -felide-constructors -Wreorder -c ptlib/common/jidctflt.cxx -o /home/nfs/extra/src/video/Ekiga/Ekiga-2008-12-29/ptlib/lib_linux_x86/obj_d/jidctflt.o > > /tmp/ccJhh47h.s: Assembler messages: > > /tmp/ccJhh47h.s:1101: Error: suffix or operands invalid for `sar' > > make[2]: *** [/home/nfs/extra/src/video/Ekiga/Ekiga-2008-12-29/ptlib/lib_linux_x86/obj_d/jidctflt.o] Fehler 1 > > make[2]: Leaving directory `/home/nfs/extra/src/video/Ekiga/Ekiga-2008-12-29/ptlib/src' > > make[1]: *** [debug] Fehler 2 > > make[1]: Leaving directory `/home/nfs/extra/src/video/Ekiga/Ekiga-2008-12-29/ptlib/src' > > make: *** [debug] Fehler 2 > > Hi, > > Do you use gcc or other compiler? What version? Are you on a 64-bit > machine? Intel or AMD? > > It seems to me that your uP does not know the assembler code in > jidctflt.cxx:110. As a workaround, you can put the 'else' branch in the > 'then' too. Thanks, workaround works. ptlib could be build with DEBUG=1. opal could be build after --enable-debug too: stefan at jarada /home/nfs/extra/src/video/Ekiga/Ekiga-2008-12-29 $ ll /usr/lib/lib*opa* -rwxr-xr-x 1 root root 73310760 31. Dez 13:44 /usr/lib/libopal_d_s.a lrwxrwxrwx 1 root root 22 31. Dez 13:44 /usr/lib/libopal_d.so -> libopal_d.so.3.5-beta2 -rwxr-xr-x 1 root root 51471518 31. Dez 13:44 /usr/lib/libopal_d.so.3.5-beta2 But it looks like ekiga itself is still insisting on a nondebugging version of libopal :-( . g++ -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/pixman-1 -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DORBIT2=1 -pthread -I/usr/include/libgnome-2.0 -I/usr/include/orbit-2.0 -I/usr/include/gconf/2 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/libgnomeui-2.0 -I/usr/include/libart-2.0 -I/usr/include/gnome-keyring-1 -I/usr/include/libbonoboui-2.0 -I/usr/include/libgnomecanvas-2.0 -I/usr/include/gtk-2.0 -I/usr/include/libxml2 -I/usr/include/pango-1.0 -I/usr/include/gail-1.0 -I/usr/include/freetype2 -I/usr/include/atk-1.0 -I/usr/lib/gtk-2.0/include -I/usr/include/cairo -I/usr/include/libpng12 -I/usr/include/pixman-1 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DPTRACING=1 -D_REENTRANT -D_GNU_SOURCE=1 -fno-exceptions -I/usr/include/opal -I/usr/include/SDL -DPTRACING=1 -D_REENTRANT -D_GNU_SOURCE=1 -fno-exceptions -I/usr/include/SDL -I/usr/include/sigc++-2.0 -I/usr/lib/sigc++-2.0/include -I/usr/include/libxml2 -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/pixman-1 -g -O2 -Wall -Wextra -Winit-self -Wswitch-default -Wswitch-enum -Wstrict-aliasing=2 -Wfloat-equal -Wshadow -o ekiga accounts.o callbacks.o conf.o dialpad.o assistant.o main.o misc.o preferences.o statusicon.o statusmenu.o ekiga.o dbus.o -Wl,--export-dynamic -pthread -pthread ../lib/.libs/libekiga.a ../lib/engine/.libs/libekiga_engine.a /usr/lib/libXv.so /usr/lib/libXext.so /usr/lib/libebook-1.2.so -L/usr/lib/nspr -L/usr/lib/lib -L/usr/lib/nss /usr/lib/libcamel-1.2.so -lssl3 -lsmime3 -lnss3 /usr/lib/libedataserver-1.2.so -lplds4 -lplc4 -lnspr4 -ldb /usr/lib/libldap.so /usr/lib/liblber.so /usr/lib/libgnomeui-2.so /usr/lib/libgio-2.0.so /usr/lib/libgnome-keyring.so /usr/lib/libjpeg.so /usr/lib/libbonoboui-2.so /usr/lib/libSM.so /usr/lib/libICE.so /usr/lib/libgnomecanvas-2.so /usr/lib/libgailutil.so /usr/lib/libgnome-2.so /usr/lib/libgnomevfs-2.so /usr/lib/libavahi-glib.so /usr/lib/libavahi-client.so /usr/lib/libavahi-common.so -lutil /usr/lib/libpopt.so /usr/lib/libbonobo-2.so /usr/lib/libbonobo-activation.so /usr/lib/libORBitCosNaming-2.so /usr/lib/libart_lgpl_2.so /usr/lib/libgconf-2.so /usr/lib/libORBit-2.so /usr/lib/libgthread-2.0.so -lrt -lopal /usr/lib/libspeexdsp.so -lpt /usr/lib/libsasl2.so -lcrypt -lssl -lcrypto /usr/lib/libSDL.so -lpthread /usr/lib/libsigc-2.0.so /usr/lib/libnotify.so /usr/lib/libgtk-x11-2.0.so /usr/lib/libdbus-glib-1.so -lnsl /usr/lib/libgdk-x11-2.0.so /usr/lib/libatk-1.0.so /usr/lib/libgdk_pixbuf-2.0.so /usr/lib/libpangocairo-1.0.so /usr/lib/libpangoft2-1.0.so /usr/lib/libxml2.so /usr/lib/libpango-1.0.so /usr/lib/libcairo.so /usr/lib/libfontconfig.so /usr/lib/libfreetype.so /usr/lib/libexpat.so /usr/lib/libpng12.so -lz /usr/lib/libXrender.so /usr/lib/libX11.so /usr/lib/libXau.so /usr/lib/libXdmcp.so /usr/lib/libpixman-1.so -lm /usr/lib/libgmodule-2.0.so -ldl /usr/lib/libdbus-1.so /usr/lib/libgobject-2.0.so /usr/lib/libglib-2.0.so -lresolv /usr/lib/gcc/i686-pc-linux-gnu/4.1.2/../../../../i686-pc-linux-gnu/bin/ld: cannot find -lopal collect2: ld returned 1 exit status make[3]: *** [ekiga] Fehler 1 -- Stefan Lucke From stefan at lucke.in-berlin.de Wed Dec 31 13:27:18 2008 From: stefan at lucke.in-berlin.de (Stefan Lucke) Date: Wed, 31 Dec 2008 14:27:18 +0100 Subject: [Ekiga-list] Segfault when theora is first codec in list. Message-ID: <200812311427.18458.stefan@lucke.in-berlin.de> Hi, sorry for next bug report. I receive a segfault when theora is the first entry of available codec list. Segfault happens when the connection is accepted. This is between ekiga 3.0.2beta WinXP and ekiga-svn (was the same with ekiga 3.0.1) on linux. GNU gdb 6.7.1 Copyright (C) 2007 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i686-pc-linux-gnu"... Using host libthread_db library "/lib/libthread_db.so.1". (gdb) run Starting program: /usr/bin/ekiga [Thread debugging using libthread_db enabled] [New Thread 0xb5f1f6d0 (LWP 14978)] [New Thread 0xb521db90 (LWP 14984)] [New Thread 0xb51dcb90 (LWP 14985)] [New Thread 0xb519bb90 (LWP 14986)] [New Thread 0xb515ab90 (LWP 14987)] [New Thread 0xb5119b90 (LWP 14988)] [New Thread 0xb50d8b90 (LWP 14989)] [New Thread 0xb5097b90 (LWP 14990)] [New Thread 0xb5056b90 (LWP 14991)] [New Thread 0xb4effb90 (LWP 14992)] [New Thread 0xb4ebeb90 (LWP 14993)] [New Thread 0xb46bdb90 (LWP 15002)] [New Thread 0xaf6fdb90 (LWP 15009)] [Thread 0xaf6fdb90 (LWP 15009) exited] [Thread 0xb4effb90 (LWP 14992) exited] [Thread 0xb5097b90 (LWP 14990) exited] [New Thread 0xb5097b90 (LWP 15011)] [Thread 0xb5056b90 (LWP 14991) exited] [New Thread 0xb5056b90 (LWP 15012)] [New Thread 0xb4effb90 (LWP 15013)] [Thread 0xb4effb90 (LWP 15013) exited] [New Thread 0xb4effb90 (LWP 15014)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb4effb90 (LWP 15014)] 0xb6050cbc in memcpy () from /lib/libc.so.6 (gdb) thread apply all bt Thread 17 (Thread 0xb4effb90 (LWP 15014)): #0 0xb6050cbc in memcpy () from /lib/libc.so.6 #1 0xb5a0afe8 in theoraFrame::SetFromTableConfig () from /usr/lib/opal-3.5.2/codecs/video/theora_video_pwplugin.so #2 0xb5a0d70e in theoraEncoderContext::theoraEncoderContext () from /usr/lib/opal-3.5.2/codecs/video/theora_video_pwplugin.so #3 0xb5a0d758 in create_encoder () from /usr/lib/opal-3.5.2/codecs/video/theora_video_pwplugin.so #4 0xb7790a5a in OpalPluginTranscoder::OpalPluginTranscoder () from /usr/lib/libopal.so.3.5-beta2 #5 0xb7791314 in OpalPluginVideoTranscoder::OpalPluginVideoTranscoder () from /usr/lib/libopal.so.3.5-beta2 #6 0xb779bacc in OpalPluginTranscoderFactory::Worker::Create () from /usr/lib/libopal.so.3.5-beta2 #7 0xb7494f38 in PFactory >::WorkerBase::CreateInstance () from /usr/lib/libopal.so.3.5-beta2 #8 0xb7496137 in PFactory >::CreateInstance_Internal () from /usr/lib/libopal.so.3.5-beta2 #9 0xb7496174 in PFactory >::CreateInstance () from /usr/lib/libopal.so.3.5-beta2 #10 0xb7494361 in OpalTranscoder::Create () from /usr/lib/libopal.so.3.5-beta2 #11 0xb7491a8f in OpalMediaPatch::AddSink () from /usr/lib/libopal.so.3.5-beta2 #12 0xb747de20 in OpalCall::OpenSourceMediaStreams () from /usr/lib/libopal.so.3.5-beta2 #13 0xb7745653 in SIPConnection::OnReceivedSDPMediaDescription () from /usr/lib/libopal.so.3.5-beta2 #14 0xb77423a5 in SIPConnection::OnReceivedSDP () from /usr/lib/libopal.so.3.5-beta2 #15 0xb7743b32 in SIPConnection::OnReceivedOK () from /usr/lib/libopal.so.3.5-beta2 #16 0xb774161e in SIPConnection::OnReceivedResponse () from /usr/lib/libopal.so.3.5-beta2 #17 0xb7756d80 in SIPTransaction::OnReceivedResponse () from /usr/lib/libopal.so.3.5-beta2 #18 0xb7759f44 in SIPInvite::OnReceivedResponse () from /usr/lib/libopal.so.3.5-beta2 #19 0xb7738ac3 in SIPEndPoint::SIP_PDU_Thread::Main () from /usr/lib/libopal.so.3.5-beta2 #20 0xb7037115 in PThread::PX_ThreadStart () from /usr/lib/libpt.so.2.5-beta2 #21 0xb6c1118b in start_thread () from /lib/libpthread.so.0 #22 0xb60a409e in clone () from /lib/libc.so.6 With a selfmade trace message in 'opal/plugins/video/THEORA/theora_frame.cxx' I get the following output with option -d 4: stefan at jarada ~ $ tail -n 20 xx6 2008/12/31 12:27:21.440 0:18.328 Aggregator:0xb4f3cb90 PVidInDev G_PARM failed (preserving frame rate may not work) : Das Argument ist ung?ltig 2008/12/31 12:27:21.440 0:18.328 Aggregator:0xb4f3cb90 PVidInDev unable to reset frame rate. 2008/12/31 12:27:21.440 0:18.328 Aggregator:0xb4f3cb90 PVidDev Colour converter used from 320x240 [YUV420P] to 176x144 [YUV420P] 2008/12/31 12:27:22.341 0:19.229 AudioEvent...0xb5220b90 AEScheduler Checking pending list with 1 elements 2008/12/31 12:27:22.341 0:19.229 AudioEvent...0xb5220b90 AEScheduler Trying to load /usr/share/sounds/ekiga/dialtone.wav for event ring_tone_sound 2008/12/31 12:27:22.342 0:19.230 AudioEvent...0xb5220b90 AudioOutputCore Dropping sound event, primary device not set 2008/12/31 12:27:23.993 0:20.881 Aggregator:0xb4f3cb90 PVidDev SetColourFormatConverter success for native YUV420P 2008/12/31 12:27:23.994 0:20.882 Aggregator:0xb4f3cb90 OpalMan OnOpenMediaStream Call[g5c0bb3d61]-EP[1],OpalVideoMediaStream-Source-YUV420P 2008/12/31 12:27:23.994 0:20.882 Aggregator:0xb4f3cb90 OpalCon Opened source stream g5c0bb3d61_2 with format YUV420P 2008/12/31 12:27:23.994 0:20.882 Aggregator:0xb4f3cb90 Call IsMediaBypassPossible Call[g5c0bb3d61]-EP[dc4443a5-9bd5-dd11-8e73-00138fd10815 at jarada] session 2 2008/12/31 12:27:23.994 0:20.882 Aggregator:0xb4f3cb90 OpalMan IsMediaBypassPossible: session 2 2008/12/31 12:27:23.994 0:20.882 Aggregator:0xb4f3cb90 OpalCon IsMediaBypassPossible: default returns false 2008/12/31 12:27:23.994 0:20.882 Aggregator:0xb4f3cb90 RTP Found existing media session 2 2008/12/31 12:27:23.995 0:20.883 Aggregator:0xb4f3cb90 OpalMan OnOpenMediaStream Call[g5c0bb3d61]-EP[dc4443a5-9bd5-dd11-8e73-00138fd10815 at jarada],OpalRTPMediaStream-Sink-theora 2008/12/31 12:27:23.995 0:20.883 Aggregator:0xb4f3cb90 OpalCon Opened sink stream g5c0bb3d61_2 with format theora 2008/12/31 12:27:23.995 0:20.883 Aggregator:0xb4f3cb90 RateController New paramaters: bitrate=1024000, window=500, frame time=3000(rate=30), max skipped frames=1 2008/12/31 12:27:23.995 0:20.883 Aggregator:0xb4f3cb90 Patch Created Sink: format=theora theora_frame.cxx(75) THEORA Encap Got Header Packet from encoder that has len 148 != 42 SetFromTableConfig len = -1240923378 (0xb609030e) h264helper_unix.cxx(72) H264 IPC CP: Terminating My change: void theoraFrame::SetFromTableConfig (ogg_packet* tablePacket) { TRACE_UP(4, "THEORA\tEncap\tGot table packet with len " << tablePacket->bytes); fprintf(stderr, "SetFromTableConfig len = %d (0x%08x)\n", tablePacket->bytes, tablePacket->bytes); memcpy (_packedConfigData.ptr + THEORA_HEADER_PACKET_SIZE, tablePacket->packet, tablePacket->bytes); .. As on my system ogg_packet->bytes is of size long, negative values of bytes should be checked and rejected like in ffmpeg (libavcodec/libtheoraenc.c). Such values could be source of stack overflows and other type of intrusion. -- Stefan Lucke From dsandras at seconix.com Wed Dec 31 13:52:48 2008 From: dsandras at seconix.com (Damien Sandras) Date: Wed, 31 Dec 2008 14:52:48 +0100 Subject: [Ekiga-list] Error message when exiting ekiga. In-Reply-To: <200812311424.18784.stefan@lucke.in-berlin.de> References: <200812310948.54656.stefan@lucke.in-berlin.de> <200812311145.03140.stefan@lucke.in-berlin.de> <495B5026.2020601@pu-pm.univ-fcomte.fr> <200812311424.18784.stefan@lucke.in-berlin.de> Message-ID: <1230731568.20800.25.camel@scorpion.multitel.be> Le mercredi 31 d?cembre 2008 ? 14:24 +0100, Stefan Lucke a ?crit : > On Wednesday 31 December 2008, Eugen Dedu wrote: > > Stefan Lucke wrote: > > > On Wednesday 31 December 2008, Damien Sandras wrote: > > >> Le mercredi 31 d?cembre 2008 ? 09:48 +0100, Stefan Lucke a ?crit : > > >>> Hi, > > >>> > > >>> I get the following error message upon exiting ekiga: > > >>> > > >>> stefan at jarada ~ $ date;ekiga;date > > >>> Mi 31. Dez 09:46:28 CET 2008 > > >>> assert.cxx(108) PWLib Assertion fail: Function pthread_mutex_lock failed, file ptlib/unix/tlibthrd.cxx, line 1304 > > >>> Assertion fail: Function pthread_mutex_lock failed, file ptlib/unix/tlibthrd.cxx, line 1304 > > >>> > > >>> bort, ore dump? A > > >>> > > >>> Aborting. > > >>> Mi 31. Dez 09:46:41 CET 2008 > > >>> > > >>> I'm using svn checkout of ekiga from 2008-12-29. > > >>> Should I provide a dump or some other debug information or report this problem elsewhere? > > >> > > >> A full GDB backtrace (see the wiki for more details on > > >> http://wiki.ekiga.org). > > > > > > ptlib cannot be build with: 'make DEBUG=1 debug' and thus opal cannot > > > be confgured with --enable-debug when ptlib is build without DEBUG=1. > > > > > > cxx -o /home/nfs/extra/src/video/Ekiga/Ekiga-2008-12-29/ptlib/lib_linux_x86/obj_d/tinyjpeg.o > > > g++ -DPTRACING=1 -D_REENTRANT -D_GNU_SOURCE=1 -D_REENTRANT -I/usr/include/SDL -fno-exceptions -Wall -fPIC -DPIC -g3 -ggdb -O0 -D_DEBUG -I/home/nfs/extra/src/video/Ekiga/Ekiga-2008-12-29/ptlib/include -felide-constructors -Wreorder -c ptlib/common/jidctflt.cxx -o /home/nfs/extra/src/video/Ekiga/Ekiga-2008-12-29/ptlib/lib_linux_x86/obj_d/jidctflt.o > > > /tmp/ccJhh47h.s: Assembler messages: > > > /tmp/ccJhh47h.s:1101: Error: suffix or operands invalid for `sar' > > > make[2]: *** [/home/nfs/extra/src/video/Ekiga/Ekiga-2008-12-29/ptlib/lib_linux_x86/obj_d/jidctflt.o] Fehler 1 > > > make[2]: Leaving directory `/home/nfs/extra/src/video/Ekiga/Ekiga-2008-12-29/ptlib/src' > > > make[1]: *** [debug] Fehler 2 > > > make[1]: Leaving directory `/home/nfs/extra/src/video/Ekiga/Ekiga-2008-12-29/ptlib/src' > > > make: *** [debug] Fehler 2 > > > > Hi, > > > > Do you use gcc or other compiler? What version? Are you on a 64-bit > > machine? Intel or AMD? > > > > It seems to me that your uP does not know the assembler code in > > jidctflt.cxx:110. As a workaround, you can put the 'else' branch in the > > 'then' too. > > Thanks, workaround works. ptlib could be build with DEBUG=1. > > opal could be build after --enable-debug too: > stefan at jarada /home/nfs/extra/src/video/Ekiga/Ekiga-2008-12-29 $ ll /usr/lib/lib*opa* > -rwxr-xr-x 1 root root 73310760 31. Dez 13:44 /usr/lib/libopal_d_s.a > lrwxrwxrwx 1 root root 22 31. Dez 13:44 /usr/lib/libopal_d.so -> libopal_d.so.3.5-beta2 > -rwxr-xr-x 1 root root 51471518 31. Dez 13:44 /usr/lib/libopal_d.so.3.5-beta2 > > But it looks like ekiga itself is still insisting on a nondebugging version of libopal :-( . You need to use --enable-opal-debug as configure switch. (./configure --help) -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From dsandras at seconix.com Wed Dec 31 13:53:50 2008 From: dsandras at seconix.com (Damien Sandras) Date: Wed, 31 Dec 2008 14:53:50 +0100 Subject: [Ekiga-list] Segfault when theora is first codec in list. In-Reply-To: <200812311427.18458.stefan@lucke.in-berlin.de> References: <200812311427.18458.stefan@lucke.in-berlin.de> Message-ID: <1230731630.20800.27.camel@scorpion.multitel.be> Le mercredi 31 d?cembre 2008 ? 14:27 +0100, Stefan Lucke a ?crit : > Hi, > > sorry for next bug report. > I receive a segfault when theora is the first entry of available codec list. > Segfault happens when the connection is accepted. > This is between ekiga 3.0.2beta WinXP and > ekiga-svn (was the same with ekiga 3.0.1) on linux. > > > GNU gdb 6.7.1 > Copyright (C) 2007 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or later > This is free software: you are free to change and redistribute it. > There is NO WARRANTY, to the extent permitted by law. Type "show copying" > and "show warranty" for details. > This GDB was configured as "i686-pc-linux-gnu"... > Using host libthread_db library "/lib/libthread_db.so.1". > (gdb) run > Starting program: /usr/bin/ekiga > [Thread debugging using libthread_db enabled] > [New Thread 0xb5f1f6d0 (LWP 14978)] > [New Thread 0xb521db90 (LWP 14984)] > [New Thread 0xb51dcb90 (LWP 14985)] > [New Thread 0xb519bb90 (LWP 14986)] > [New Thread 0xb515ab90 (LWP 14987)] > [New Thread 0xb5119b90 (LWP 14988)] > [New Thread 0xb50d8b90 (LWP 14989)] > [New Thread 0xb5097b90 (LWP 14990)] > [New Thread 0xb5056b90 (LWP 14991)] > [New Thread 0xb4effb90 (LWP 14992)] > [New Thread 0xb4ebeb90 (LWP 14993)] > [New Thread 0xb46bdb90 (LWP 15002)] > [New Thread 0xaf6fdb90 (LWP 15009)] > [Thread 0xaf6fdb90 (LWP 15009) exited] > [Thread 0xb4effb90 (LWP 14992) exited] > [Thread 0xb5097b90 (LWP 14990) exited] > [New Thread 0xb5097b90 (LWP 15011)] > [Thread 0xb5056b90 (LWP 14991) exited] > [New Thread 0xb5056b90 (LWP 15012)] > [New Thread 0xb4effb90 (LWP 15013)] > [Thread 0xb4effb90 (LWP 15013) exited] > [New Thread 0xb4effb90 (LWP 15014)] > > Program received signal SIGSEGV, Segmentation fault. > [Switching to Thread 0xb4effb90 (LWP 15014)] > 0xb6050cbc in memcpy () from /lib/libc.so.6 > (gdb) thread apply all bt > > Thread 17 (Thread 0xb4effb90 (LWP 15014)): > #0 0xb6050cbc in memcpy () from /lib/libc.so.6 > #1 0xb5a0afe8 in theoraFrame::SetFromTableConfig () from /usr/lib/opal-3.5.2/codecs/video/theora_video_pwplugin.so > #2 0xb5a0d70e in theoraEncoderContext::theoraEncoderContext () > from /usr/lib/opal-3.5.2/codecs/video/theora_video_pwplugin.so > #3 0xb5a0d758 in create_encoder () from /usr/lib/opal-3.5.2/codecs/video/theora_video_pwplugin.so > #4 0xb7790a5a in OpalPluginTranscoder::OpalPluginTranscoder () from /usr/lib/libopal.so.3.5-beta2 > #5 0xb7791314 in OpalPluginVideoTranscoder::OpalPluginVideoTranscoder () from /usr/lib/libopal.so.3.5-beta2 > #6 0xb779bacc in OpalPluginTranscoderFactory::Worker::Create () > from /usr/lib/libopal.so.3.5-beta2 > #7 0xb7494f38 in PFactory >::WorkerBase::CreateInstance () > from /usr/lib/libopal.so.3.5-beta2 > #8 0xb7496137 in PFactory >::CreateInstance_Internal () > from /usr/lib/libopal.so.3.5-beta2 > #9 0xb7496174 in PFactory >::CreateInstance () > from /usr/lib/libopal.so.3.5-beta2 > #10 0xb7494361 in OpalTranscoder::Create () from /usr/lib/libopal.so.3.5-beta2 > #11 0xb7491a8f in OpalMediaPatch::AddSink () from /usr/lib/libopal.so.3.5-beta2 > #12 0xb747de20 in OpalCall::OpenSourceMediaStreams () from /usr/lib/libopal.so.3.5-beta2 > #13 0xb7745653 in SIPConnection::OnReceivedSDPMediaDescription () from /usr/lib/libopal.so.3.5-beta2 > #14 0xb77423a5 in SIPConnection::OnReceivedSDP () from /usr/lib/libopal.so.3.5-beta2 > #15 0xb7743b32 in SIPConnection::OnReceivedOK () from /usr/lib/libopal.so.3.5-beta2 > #16 0xb774161e in SIPConnection::OnReceivedResponse () from /usr/lib/libopal.so.3.5-beta2 > #17 0xb7756d80 in SIPTransaction::OnReceivedResponse () from /usr/lib/libopal.so.3.5-beta2 > #18 0xb7759f44 in SIPInvite::OnReceivedResponse () from /usr/lib/libopal.so.3.5-beta2 > #19 0xb7738ac3 in SIPEndPoint::SIP_PDU_Thread::Main () from /usr/lib/libopal.so.3.5-beta2 > #20 0xb7037115 in PThread::PX_ThreadStart () from /usr/lib/libpt.so.2.5-beta2 > #21 0xb6c1118b in start_thread () from /lib/libpthread.so.0 > #22 0xb60a409e in clone () from /lib/libc.so.6 > > With a selfmade trace message in 'opal/plugins/video/THEORA/theora_frame.cxx' > I get the following output with option -d 4: > > stefan at jarada ~ $ tail -n 20 xx6 > 2008/12/31 12:27:21.440 0:18.328 Aggregator:0xb4f3cb90 PVidInDev G_PARM failed (preserving frame rate may not work) : Das Argument ist ung?ltig > 2008/12/31 12:27:21.440 0:18.328 Aggregator:0xb4f3cb90 PVidInDev unable to reset frame rate. > 2008/12/31 12:27:21.440 0:18.328 Aggregator:0xb4f3cb90 PVidDev Colour converter used from 320x240 [YUV420P] to 176x144 [YUV420P] > 2008/12/31 12:27:22.341 0:19.229 AudioEvent...0xb5220b90 AEScheduler Checking pending list with 1 elements > 2008/12/31 12:27:22.341 0:19.229 AudioEvent...0xb5220b90 AEScheduler Trying to load /usr/share/sounds/ekiga/dialtone.wav for event ring_tone_sound > 2008/12/31 12:27:22.342 0:19.230 AudioEvent...0xb5220b90 AudioOutputCore Dropping sound event, primary device not set > 2008/12/31 12:27:23.993 0:20.881 Aggregator:0xb4f3cb90 PVidDev SetColourFormatConverter success for native YUV420P > 2008/12/31 12:27:23.994 0:20.882 Aggregator:0xb4f3cb90 OpalMan OnOpenMediaStream Call[g5c0bb3d61]-EP[1],OpalVideoMediaStream-Source-YUV420P > 2008/12/31 12:27:23.994 0:20.882 Aggregator:0xb4f3cb90 OpalCon Opened source stream g5c0bb3d61_2 with format YUV420P > 2008/12/31 12:27:23.994 0:20.882 Aggregator:0xb4f3cb90 Call IsMediaBypassPossible Call[g5c0bb3d61]-EP[dc4443a5-9bd5-dd11-8e73-00138fd10815 at jarada] session 2 > 2008/12/31 12:27:23.994 0:20.882 Aggregator:0xb4f3cb90 OpalMan IsMediaBypassPossible: session 2 > 2008/12/31 12:27:23.994 0:20.882 Aggregator:0xb4f3cb90 OpalCon IsMediaBypassPossible: default returns false > 2008/12/31 12:27:23.994 0:20.882 Aggregator:0xb4f3cb90 RTP Found existing media session 2 > 2008/12/31 12:27:23.995 0:20.883 Aggregator:0xb4f3cb90 OpalMan OnOpenMediaStream Call[g5c0bb3d61]-EP[dc4443a5-9bd5-dd11-8e73-00138fd10815 at jarada],OpalRTPMediaStream-Sink-theora > 2008/12/31 12:27:23.995 0:20.883 Aggregator:0xb4f3cb90 OpalCon Opened sink stream g5c0bb3d61_2 with format theora > 2008/12/31 12:27:23.995 0:20.883 Aggregator:0xb4f3cb90 RateController New paramaters: bitrate=1024000, window=500, frame time=3000(rate=30), max skipped frames=1 > 2008/12/31 12:27:23.995 0:20.883 Aggregator:0xb4f3cb90 Patch Created Sink: format=theora > theora_frame.cxx(75) THEORA Encap Got Header Packet from encoder that has len 148 != 42 > SetFromTableConfig len = -1240923378 (0xb609030e) > h264helper_unix.cxx(72) H264 IPC CP: Terminating > > My change: > void theoraFrame::SetFromTableConfig (ogg_packet* tablePacket) { > TRACE_UP(4, "THEORA\tEncap\tGot table packet with len " << tablePacket->bytes); > fprintf(stderr, "SetFromTableConfig len = %d (0x%08x)\n", tablePacket->bytes, tablePacket->bytes); > memcpy (_packedConfigData.ptr + THEORA_HEADER_PACKET_SIZE, tablePacket->packet, tablePacket->bytes); > .. > > As on my system ogg_packet->bytes is of size long, negative values of > bytes should be checked and rejected like in ffmpeg (libavcodec/libtheoraenc.c). > Such values could be source of stack overflows and other type of intrusion. > It is weird. Wouldn't you have hard optimization values for compiling like -O3 or such ? If not, could you propose a patch ? 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:dsandras at ekiga.net From stefan at lucke.in-berlin.de Wed Dec 31 14:38:58 2008 From: stefan at lucke.in-berlin.de (Stefan Lucke) Date: Wed, 31 Dec 2008 15:38:58 +0100 Subject: [Ekiga-list] Error message when exiting ekiga. In-Reply-To: <1230731568.20800.25.camel@scorpion.multitel.be> References: <200812310948.54656.stefan@lucke.in-berlin.de> <200812311424.18784.stefan@lucke.in-berlin.de> <1230731568.20800.25.camel@scorpion.multitel.be> Message-ID: <200812311538.59035.stefan@lucke.in-berlin.de> On Wednesday 31 December 2008, Damien Sandras wrote: > Le mercredi 31 d?cembre 2008 ? 14:24 +0100, Stefan Lucke a ?crit : > > On Wednesday 31 December 2008, Eugen Dedu wrote: > > > Stefan Lucke wrote: > > > > On Wednesday 31 December 2008, Damien Sandras wrote: > > > >> Le mercredi 31 d?cembre 2008 ? 09:48 +0100, Stefan Lucke a ?crit : > > > >>> Hi, > > > >>> > > > >>> I get the following error message upon exiting ekiga: > > > >>> > > > >>> stefan at jarada ~ $ date;ekiga;date > > > >>> Mi 31. Dez 09:46:28 CET 2008 > > > >>> assert.cxx(108) PWLib Assertion fail: Function pthread_mutex_lock failed, file ptlib/unix/tlibthrd.cxx, line 1304 > > > >>> Assertion fail: Function pthread_mutex_lock failed, file ptlib/unix/tlibthrd.cxx, line 1304 > > > >>> > > > >>> bort, ore dump? A > > > >>> > > > >>> Aborting. > > > >>> Mi 31. Dez 09:46:41 CET 2008 > > > >>> > > > >>> I'm using svn checkout of ekiga from 2008-12-29. > > > >>> Should I provide a dump or some other debug information or report this problem elsewhere? > > > >> > > > >> A full GDB backtrace (see the wiki for more details on > > > >> http://wiki.ekiga.org). > > > > > > > > ptlib cannot be build with: 'make DEBUG=1 debug' and thus opal cannot > > > > be confgured with --enable-debug when ptlib is build without DEBUG=1. > > > > > > > > cxx -o /home/nfs/extra/src/video/Ekiga/Ekiga-2008-12-29/ptlib/lib_linux_x86/obj_d/tinyjpeg.o > > > > g++ -DPTRACING=1 -D_REENTRANT -D_GNU_SOURCE=1 -D_REENTRANT -I/usr/include/SDL -fno-exceptions -Wall -fPIC -DPIC -g3 -ggdb -O0 -D_DEBUG -I/home/nfs/extra/src/video/Ekiga/Ekiga-2008-12-29/ptlib/include -felide-constructors -Wreorder -c ptlib/common/jidctflt.cxx -o /home/nfs/extra/src/video/Ekiga/Ekiga-2008-12-29/ptlib/lib_linux_x86/obj_d/jidctflt.o > > > > /tmp/ccJhh47h.s: Assembler messages: > > > > /tmp/ccJhh47h.s:1101: Error: suffix or operands invalid for `sar' > > > > make[2]: *** [/home/nfs/extra/src/video/Ekiga/Ekiga-2008-12-29/ptlib/lib_linux_x86/obj_d/jidctflt.o] Fehler 1 > > > > make[2]: Leaving directory `/home/nfs/extra/src/video/Ekiga/Ekiga-2008-12-29/ptlib/src' > > > > make[1]: *** [debug] Fehler 2 > > > > make[1]: Leaving directory `/home/nfs/extra/src/video/Ekiga/Ekiga-2008-12-29/ptlib/src' > > > > make: *** [debug] Fehler 2 > > > > > > Hi, > > > > > > Do you use gcc or other compiler? What version? Are you on a 64-bit > > > machine? Intel or AMD? > > > > > > It seems to me that your uP does not know the assembler code in > > > jidctflt.cxx:110. As a workaround, you can put the 'else' branch in the > > > 'then' too. > > > > Thanks, workaround works. ptlib could be build with DEBUG=1. > > > > opal could be build after --enable-debug too: > > stefan at jarada /home/nfs/extra/src/video/Ekiga/Ekiga-2008-12-29 $ ll /usr/lib/lib*opa* > > -rwxr-xr-x 1 root root 73310760 31. Dez 13:44 /usr/lib/libopal_d_s.a > > lrwxrwxrwx 1 root root 22 31. Dez 13:44 /usr/lib/libopal_d.so -> libopal_d.so.3.5-beta2 > > -rwxr-xr-x 1 root root 51471518 31. Dez 13:44 /usr/lib/libopal_d.so.3.5-beta2 > > > > But it looks like ekiga itself is still insisting on a nondebugging version of libopal :-( . > > You need to use --enable-opal-debug as configure switch. (./configure > --help) Thanks, only found --enable-debug. Builds fine now. -- Stefan Lucke From stefan at lucke.in-berlin.de Wed Dec 31 14:40:33 2008 From: stefan at lucke.in-berlin.de (Stefan Lucke) Date: Wed, 31 Dec 2008 15:40:33 +0100 Subject: [Ekiga-list] Error message when exiting ekiga. In-Reply-To: <1230715892.20800.11.camel@scorpion.multitel.be> References: <200812310948.54656.stefan@lucke.in-berlin.de> <1230715892.20800.11.camel@scorpion.multitel.be> Message-ID: <200812311540.34042.stefan@lucke.in-berlin.de> On Wednesday 31 December 2008, Damien Sandras wrote: > Le mercredi 31 d?cembre 2008 ? 09:48 +0100, Stefan Lucke a ?crit : > > Hi, > > > > I get the following error message upon exiting ekiga: > > > > stefan at jarada ~ $ date;ekiga;date > > Mi 31. Dez 09:46:28 CET 2008 > > assert.cxx(108) PWLib Assertion fail: Function pthread_mutex_lock failed, file ptlib/unix/tlibthrd.cxx, line 1304 > > Assertion fail: Function pthread_mutex_lock failed, file ptlib/unix/tlibthrd.cxx, line 1304 > > > > bort, ore dump? A > > > > Aborting. > > Mi 31. Dez 09:46:41 CET 2008 > > > > I'm using svn checkout of ekiga from 2008-12-29. > > Should I provide a dump or some other debug information or report this problem elsewhere? > > > A full GDB backtrace (see the wiki for more details on > http://wiki.ekiga.org). Hopefully attached file helps. -- Stefan Lucke -------------- next part -------------- A non-text attachment was scrubbed... Name: ekiga-debug-assert-failed-00.script.bz2 Type: application/x-bzip2 Size: 3853 bytes Desc: not available URL: From bnc at astronomicalresearchaustralia.org Wed Dec 31 16:11:20 2008 From: bnc at astronomicalresearchaustralia.org (Brian) Date: Thu, 01 Jan 2009 02:11:20 +1000 Subject: [Ekiga-list] Compile Problem In-Reply-To: <495B4E1C.90203@pu-pm.univ-fcomte.fr> References: <49556360.000002.20513@kamasutra> <4955853F.4090407@astronomicalresearchaustralia.org> <1230373752.24875.14.camel@scorpion.multitel.be> <49562D88.6090909@astronomicalresearchaustralia.org> <1230409601.30628.0.camel@scorpion.multitel.be> <49571AD4.1010703@astronomicalresearchaustralia.org> <1230487181.4343.0.camel@scorpion.multitel.be> <49582D6C.1040901@astronomicalresearchaustralia.org> <4958A742.9060808@pu-pm.univ-fcomte.fr> <4959FC19.2070404@astronomicalresearchaustralia.org> <495A57B9.9050206@pu-pm.univ-fcomte.fr> <495AB1B6.8000303@astronomicalresearchaustralia.org> <495B4E1C.90203@pu-pm.univ-fcomte.fr> Message-ID: <495B99A8.6020206@astronomicalresearchaustralia.org> Eugen, > > In the original version (sources only), I do not have these files. > > After compilation, I do have these files, but they do not reference resmgr. > Yes it makes me think that I am picking up a file a I shouldn't, from the old 10.3 system. There should be no reference to resmgr in 11.1. I did a make clean and then started again with your configure options, except I used /user/lib. I think PTLIB and OPAL went a lot better, I definitely saw messages that seemed to be including V4L2 this time. However, on recompiling ekiga I ended up with the same resmgr problem. Next I thing I will try re extracting the tarball and start with a clean slate, but it is 03.00 and I am falling asleep. Later, Brian From peasthope at shaw.ca Wed Dec 31 17:02:16 2008 From: peasthope at shaw.ca (peasthope at shaw.ca) Date: Wed, 31 Dec 2008 10:02:16 -0700 Subject: [Ekiga-list] Re (2): Audio-Problems Message-ID: <171055711.41104.39159.@heaviside.petershouse.invalid> "Palo S." wrote, > It looks like Skype is blocking Ekiga, ... In Debian Lenny on both a generic machine and an IBM NetVista, Ekiga and Skype tolerate each other. They can not use the sound hardware simultanously of course but there should never be a reason to. What system is the conflict observed in? Does a conflict exist immediately after startup? Does a conflict only occur after a Skype conversation? Regards, ... Peter E. -- http://members.shaw.ca/peasthope/ http://carnot.yi.org/ = http://carnot.pathology.ubc.ca/ From palos at post.sk Wed Dec 31 20:18:51 2008 From: palos at post.sk (Palo S.) Date: 31 Dec 2008 21:18:51 +0100 (CET) Subject: [Ekiga-list] Re (2): Audio-Problems Message-ID: <495BD3AB.000001.11521@kamasutra> > In Debian Lenny on both a generic machine and > an IBM NetVista, Ekiga and Skype tolerate each > other. They can not use the sound hardware > simultanously of course but there should never > be a reason to. Hm, I cannot reproduce the problem anymore. I remember that the last time I used Skype (was some 2-3 months ago!) Ekiga audio did not work when Skype was running. I think it was with older versions of all Ekiga, Skype and operating system (Fedora). So I won\'t be of any help with this. Maybe Judith can provide information about her problem? Palo > > What system is the conflict observed in? > Does a conflict exist immediately after startup? > Does a conflict only occur after a Skype conversation? > > Regards, ... Peter E. > > -- > http://members.shaw.ca/peasthope/ > http://carnot.yi.org/ = http://carnot.pathology.ubc.ca/ > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > __________ http://cestovanie.sme.sk/ - Cel? svet na va?om monitore From peasthope at shaw.ca Wed Dec 31 21:24:41 2008 From: peasthope at shaw.ca (PETER EASTHOPE) Date: Wed, 31 Dec 2008 13:24:41 -0800 Subject: [Ekiga-list] Re (2): Re (2): Audio-Problems Message-ID: Palo, ps> Ekiga audio did not work when Skype was running. Do you mean that you want to hear the ring from an incoming call to Ekiga while a Skype conversation is in progress? Or do you mean that the Skype daemon is merely idle in the background when Ekiga rings? In this system, ringing is directed to the default device, which is an alias for the on-board Intel sound. Sound-in and sound-out use a USB-audio adapter and headset. If Judith's system uses the same device for sound-out and for ringing, an incoming Ekiga connection during a Skype conversation would be problematic. Conclusion: separate hardware for sound out and for ringing is a worthwhile small investment. Regards, ... Peter E. -- http://members.shaw.ca/peasthope/ http://carnot.yi.org/ = http://carnot.pathology.ubc.ca/ From federicotg at gmail.com Wed Dec 31 22:54:02 2008 From: federicotg at gmail.com (Federico Tello Gentile) Date: Wed, 31 Dec 2008 20:54:02 -0200 Subject: [Ekiga-list] Is there any registration delay when creating new ekiga.net accounts? Message-ID: <1230764042.7568.9.camel@phenom> Yesterday I registered a new account in ekiga.net, but in Ekiga 3.0.1 (ubuntu 8.10 amd64) the account state was not registered saying (in Spanish) something like "Could not register(timeout)". Later that day (about 4 hours later) the account appeared registered and works (echo test at least). Today the same happened with a new account for my brother. I recieved the email telling me the account was created, but ekiga cannot log in. Is this normal? Is there a period of time intil the new accouts are accepted by the server? I did not find anything about it in the wiki or googling. Thanks for reading.