From chinku.linux at gmail.com Mon Feb 2 10:38:48 2009 From: chinku.linux at gmail.com (chaitanya mehandru) Date: Mon, 2 Feb 2009 16:08:48 +0530 Subject: [Ekiga-list] [nylug-talk] assistance with free-ing educational text btg In-Reply-To: <1233568498.30917.1298002007@webmail.messagingengine.com> References: <20090126002420.GA14315@horacrux> <1233286747.9138.1297537503@webmail.messagingengine.com> <1233568498.30917.1298002007@webmail.messagingengine.com> Message-ID: <24b40b2b0902020238h6a961bc7s6507fea18f2577a0@mail.gmail.com> Hi, I already joined the list and said 'Hi'. My name is Chaitanya Mehandru. I am currently half way through building ekiga 3 on kde 8.04. Some issues with the Makefiles to be resolved. Can we talk about this in advance..? I have build the opal and ptlib successfully. Thanks, Chaitanya Mehandru On Mon, Feb 2, 2009 at 3:24 PM, john_re wrote: > Hi Boris :) > > Pliant looks interesting :) > > We at the BerkeleyTIP global monthly meeting are working toward having > remote persons give talks for the meeting. We've already successfully > used a VOIP conference server for several months, & have had attendees > from NorthCarolina, Michigan, Washington State & Hawaii. > > This month we might have a talk about Ekiga 3 given from India. > > Where in the world are you? Do you have VOIP capability? > > I'd suggest you join the BTIP mailing list & say "Hi", & tell us your > thoughts on what you could cover in your P talk. > > Maybe we could start with a 5 minute mini talk this Feb 7, just so we > all can better get the feel of doing live talks. :) > > We don't yet have a procedure for showing slides, or live computer > output, but that will come in time. > > I hope to hear from you on the BTIP list! :) > > > On Sat, 31 Jan 2009 10:42:46 -0500, "Boris Reitman" > said: > > Hello, > > > > I can give a presentation about the pliant programming language. > > > > BORIS > > > > Sent from my iPhone > > > > On Jan 29, 2009, at 10:39 PM, "john_re" wrote: > > > > > Hi Adam, & anyone interested in this :) > > > > > > I invite > > > 1) you to make a 5-10 min presentation about your project to > > > the BerkeleyTIP-Global meeting, Jan 7 Saturday, via VOIP. > > > 2) All your groups memebers to join in the global BTIP meeting via > > > VOIP. > > > > > > We are a monthly global (via VOIP) meeting about GNU(Linux) & BSD & > > > all > > > free sw & culture, so your effort fits right in. :) > > > http://groups.google.com/group/BerkTIP > > > Click "join this group" on the page rhs to get on the mailing list. > > > > > > I'll mention about your event on the 10-20 announcements I send out > > > about BTIP, so that might get you some more exposure, & perhaps > > > volunteers. :) > > > > > > > > > I'll pass it on to a UCB CS professor, who is interested in education > > > related topics. :) > > > > > > Is there anyone in your group who might like to give a short, 5-10 min > > > talk about what you all are doing? Maybe just before 12N pacific > > > time = > > > < 3P Eastern? > > > > > > > > > > > > On Sun, 25 Jan 2009 19:24:20 -0500, "Kevin Mark" > > > said: > > >> > > >> Forward from a fellow FLOSS supporter: > > >> > > >> If you are in the NY-area and would like to help out with the project > > >> described > > >> below, they are looking for volunteers. Help FLOSSIFY the enormously > > >> popular > > >> book Digital Foundations. The event is being hosted Feb 6-8 at the > > >> lovely > > >> Eyebeam with some Free as in Beer and Grub provided! > > >> > > >> ******************************************************* > > >> > > >> FLOSSIFY 1 : Digital Foundations > > > ... > > > > > >> Our first text book is the wonderful Digital Foundations book > > >> produced > > >> by Michael Mandiberg and Xtine Burrough > > >> (http://digital-foundations.net/). Its a text book designed to teach > > >> software by teaching design. The current toolset it uses is the Adobe > > >> Creative Suite and we will convert these examples entirely to using > > >> free > > >> software. > > >> > > >> FLOSSIFY 1 : Digital Foundations will focus on a fun 3 day event at > > >> Eyebeam, NYC. Anyone is welcome to attend and some food and beer > > >> will be > > >> provided. Come and meet some of your old geek friends, make some new, > > >> and help make a step towards unshackling education from proprietary > > >> software. > ... > > _____________________________________________________________________________ > Hire expert Linux talent by posting jobs here :: http://jobs.nylug.org > The nylug-talk mailing list is at nylug-talk at nylug.org > The list archive is at http://nylug.org/pipermail/nylug-talk > To subscribe or unsubscribe: http://nylug.org/mailman/listinfo/nylug-talk > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Eugen.Dedu at pu-pm.univ-fcomte.fr Mon Feb 2 10:49:29 2009 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Mon, 02 Feb 2009 11:49:29 +0100 Subject: [Ekiga-list] [nylug-talk] assistance with free-ing educational text btg In-Reply-To: <24b40b2b0902020238h6a961bc7s6507fea18f2577a0@mail.gmail.com> References: <20090126002420.GA14315@horacrux> <1233286747.9138.1297537503@webmail.messagingengine.com> <1233568498.30917.1298002007@webmail.messagingengine.com> <24b40b2b0902020238h6a961bc7s6507fea18f2577a0@mail.gmail.com> Message-ID: <4986CFB9.4000804@pu-pm.univ-fcomte.fr> Of course. Ask your questions. chaitanya mehandru wrote: > Hi, I already joined the list and said 'Hi'. My name is Chaitanya Mehandru. > I am currently half way through building ekiga 3 on kde 8.04. Some issues > with the Makefiles to be resolved. Can we talk about this in advance..? I > have build the opal and ptlib successfully. > Thanks, > Chaitanya Mehandru > > On Mon, Feb 2, 2009 at 3:24 PM, john_re wrote: > >> Hi Boris :) >> >> Pliant looks interesting :) >> >> We at the BerkeleyTIP global monthly meeting are working toward having >> remote persons give talks for the meeting. We've already successfully >> used a VOIP conference server for several months, & have had attendees >> from NorthCarolina, Michigan, Washington State & Hawaii. >> >> This month we might have a talk about Ekiga 3 given from India. >> >> Where in the world are you? Do you have VOIP capability? >> >> I'd suggest you join the BTIP mailing list & say "Hi", & tell us your >> thoughts on what you could cover in your P talk. >> >> Maybe we could start with a 5 minute mini talk this Feb 7, just so we >> all can better get the feel of doing live talks. :) >> >> We don't yet have a procedure for showing slides, or live computer >> output, but that will come in time. >> >> I hope to hear from you on the BTIP list! :) >> >> >> On Sat, 31 Jan 2009 10:42:46 -0500, "Boris Reitman" >> said: >>> Hello, >>> >>> I can give a presentation about the pliant programming language. >>> >>> BORIS >>> >>> Sent from my iPhone >>> >>> On Jan 29, 2009, at 10:39 PM, "john_re" wrote: >>> >>>> Hi Adam, & anyone interested in this :) >>>> >>>> I invite >>>> 1) you to make a 5-10 min presentation about your project to >>>> the BerkeleyTIP-Global meeting, Jan 7 Saturday, via VOIP. >>>> 2) All your groups memebers to join in the global BTIP meeting via >>>> VOIP. >>>> >>>> We are a monthly global (via VOIP) meeting about GNU(Linux) & BSD & >>>> all >>>> free sw & culture, so your effort fits right in. :) >>>> http://groups.google.com/group/BerkTIP >>>> Click "join this group" on the page rhs to get on the mailing list. >>>> >>>> I'll mention about your event on the 10-20 announcements I send out >>>> about BTIP, so that might get you some more exposure, & perhaps >>>> volunteers. :) >>>> >>>> >>>> I'll pass it on to a UCB CS professor, who is interested in education >>>> related topics. :) >>>> >>>> Is there anyone in your group who might like to give a short, 5-10 min >>>> talk about what you all are doing? Maybe just before 12N pacific >>>> time = >>>> < 3P Eastern? >>>> >>>> >>>> >>>> On Sun, 25 Jan 2009 19:24:20 -0500, "Kevin Mark" >>>> said: >>>>> Forward from a fellow FLOSS supporter: >>>>> >>>>> If you are in the NY-area and would like to help out with the project >>>>> described >>>>> below, they are looking for volunteers. Help FLOSSIFY the enormously >>>>> popular >>>>> book Digital Foundations. The event is being hosted Feb 6-8 at the >>>>> lovely >>>>> Eyebeam with some Free as in Beer and Grub provided! >>>>> >>>>> ******************************************************* >>>>> >>>>> FLOSSIFY 1 : Digital Foundations >>>> ... >>>> >>>>> Our first text book is the wonderful Digital Foundations book >>>>> produced >>>>> by Michael Mandiberg and Xtine Burrough >>>>> (http://digital-foundations.net/). Its a text book designed to teach >>>>> software by teaching design. The current toolset it uses is the Adobe >>>>> Creative Suite and we will convert these examples entirely to using >>>>> free >>>>> software. >>>>> >>>>> FLOSSIFY 1 : Digital Foundations will focus on a fun 3 day event at >>>>> Eyebeam, NYC. Anyone is welcome to attend and some food and beer >>>>> will be >>>>> provided. Come and meet some of your old geek friends, make some new, >>>>> and help make a step towards unshackling education from proprietary >>>>> software. >> ... >> >> _____________________________________________________________________________ >> Hire expert Linux talent by posting jobs here :: http://jobs.nylug.org >> The nylug-talk mailing list is at nylug-talk at nylug.org >> The list archive is at http://nylug.org/pipermail/nylug-talk >> To subscribe or unsubscribe: http://nylug.org/mailman/listinfo/nylug-talk From john_re at fastmail.us Mon Feb 2 11:07:42 2009 From: john_re at fastmail.us (john_re) Date: Mon, 02 Feb 2009 03:07:42 -0800 Subject: [Ekiga-list] Chiat, Ekiga3 kde 8.04 issues makefiles India BerkeleyTIP Feb 7 was- Re: [nylug-talk] assistance with free-ing educational text btg In-Reply-To: <24b40b2b0902020238h6a961bc7s6507fea18f2577a0@mail.gmail.com> References: <20090126002420.GA14315@horacrux> <1233286747.9138.1297537503@webmail.messagingengine.com> <1233568498.30917.1298002007@webmail.messagingengine.com> <24b40b2b0902020238h6a961bc7s6507fea18f2577a0@mail.gmail.com> Message-ID: <1233572862.12363.1298009919@webmail.messagingengine.com> Hi Chaitanya! :) I am actually right now, just as I received this from you, in the middle of _re-writing_ my reply to your _last_ email. <8-0 I wrote you a great reply, & then apparently with all the things I have to do I must have forgotten to send it, & that reply is now gone forever. :( I am so sad. :( Anyway, I'm so slow at writing emails, but my _re-written_ reply is half finished, & so I'm going to try to finish that first, so I'll be back up to zero level, & then work forward from there. :) The reason I'd noticed my _last_ email to you had disappeared is because I was about to write you a _new_ email asking how you are progressing, and to see if maybe we can try a test VOIP conference sometime early this week, so we can work out any bugs that might exist in having you connect to our ekiga.net VOIP conference server channel from India, before the Feb 7 meeting. So, thank you to you for this email from you, for keeping on top of things, :) As you saw in my reply to Boris below, we've successfully had people connect to our VOIP conference from the East, North, & West continental USA, plus Hawaii, out in the middle of the Pacific Ocean. But it will be a likely big step forward to get you connected from halfway around the world. :) - Hopefully an _easy_ big step. :) It is very late at night here, _way_ long past my bedtime. But, I thought it was important to get the _re-written_ email out to you tonight before I go to bed. So, it will probably not be until 12-18 hours from now that I can start to think about the issues you have just raised in this email of yours, & write a reply. == OK, so you have some makefiles issues to be resolved - please email me back, & be sure to include sending to the BTIP list, & tell us more details about what you want to talk about, & what your suggestion is for solving the problem. :) Besides myself, there are several very capable people on the BTIP list who are also able to help all of us together find solutions to any problems that come up - in particular I'll mention to you David, Daniel, Windsor & Chris. :) BTIP members - if you have suggestions for Chaitanya, please jump right in with them. :) THanks C., & best wishes. :) On Mon, 2 Feb 2009 16:08:48 +0530, "chaitanya mehandru" said: > Hi, I already joined the list and said 'Hi'. My name is Chaitanya > Mehandru. > I am currently half way through building ekiga 3 on kde 8.04. Some issues > with the Makefiles to be resolved. Can we talk about this in advance..? I > have build the opal and ptlib successfully. > Thanks, > Chaitanya Mehandru > > On Mon, Feb 2, 2009 at 3:24 PM, john_re wrote: > > > Hi Boris :) > > > > Pliant looks interesting :) > > > > We at the BerkeleyTIP global monthly meeting are working toward having > > remote persons give talks for the meeting. We've already successfully > > used a VOIP conference server for several months, & have had attendees > > from NorthCarolina, Michigan, Washington State & Hawaii. > > > This month we might have a talk about Ekiga 3 given from India. > ... From chinku.linux at gmail.com Mon Feb 2 14:45:25 2009 From: chinku.linux at gmail.com (chaitanya mehandru) Date: Mon, 2 Feb 2009 20:15:25 +0530 Subject: [Ekiga-list] 30fps on Ekiga 3.0.2 with H264 enabled Message-ID: <24b40b2b0902020645m58baebaapc8fa2a8245a7f84a@mail.gmail.com> Hi, Is it possible to reach a frame rate of 30fps on Ekiga 3.0.2 with H264 enabled on Ubuntu 8.04 ( kernel 2.6.24-23 )...? I am using the Logitech QuickCam for Notebooks Pro 2Mpixel camera. I have observed a range of transmistted / received frame from 21/9 to 26/46 with and average of 24/12 most of the time. If there is some way of achieving a ratio of 30/30, please let me know. On wiki.ekiga.org, it is mentioned that using setpwc tool, we can set the philips webcams to support 30fps. But this is limited to philips webcam only..!! Please suggest a solution for logitech camera. Thanks, Chaitanya Mehandru Thanks, Chaitanya -------------- next part -------------- An HTML attachment was scrubbed... URL: From sevmek at free.fr Mon Feb 2 17:34:29 2009 From: sevmek at free.fr (yannick) Date: Mon, 02 Feb 2009 18:34:29 +0100 Subject: [Ekiga-list] [nylug-talk] assistance with free-ing educational text btg In-Reply-To: <24b40b2b0902020238h6a961bc7s6507fea18f2577a0@mail.gmail.com> References: <20090126002420.GA14315@horacrux> <1233286747.9138.1297537503@webmail.messagingengine.com> <1233568498.30917.1298002007@webmail.messagingengine.com> <24b40b2b0902020238h6a961bc7s6507fea18f2577a0@mail.gmail.com> Message-ID: <1233596069.18030.2.camel@achille> Le lundi 02 f?vrier 2009 ? 16:08 +0530, chaitanya mehandru a ?crit : > Hi, I already joined the list and said 'Hi'. My name is Chaitanya > Mehandru. I am currently half way through building ekiga 3 on kde > 8.04. Some issues with the Makefiles to be resolved. Can we talk about > this in advance..? I have build the opal and ptlib successfully. > Hello, Will you be kind enough to document what you've done in our wiki? -> http://wiki.ekiga.org/index.php/Main_Page I can grant you a full writable access to the wiki, and open a page for this topic. Best regards, Yannick > > Thanks, > Chaitanya Mehandru > > On Mon, Feb 2, 2009 at 3:24 PM, john_re wrote: > Hi Boris :) > > Pliant looks interesting :) > > We at the BerkeleyTIP global monthly meeting are working > toward having > remote persons give talks for the meeting. We've already > successfully > used a VOIP conference server for several months, & have had > attendees > from NorthCarolina, Michigan, Washington State & Hawaii. > > This month we might have a talk about Ekiga 3 given from > India. > > Where in the world are you? Do you have VOIP capability? > > I'd suggest you join the BTIP mailing list & say "Hi", & tell > us your > thoughts on what you could cover in your P talk. > > Maybe we could start with a 5 minute mini talk this Feb 7, > just so we > all can better get the feel of doing live talks. :) > > We don't yet have a procedure for showing slides, or live > computer > output, but that will come in time. > > I hope to hear from you on the BTIP list! :) > > > > On Sat, 31 Jan 2009 10:42:46 -0500, "Boris Reitman" > said: > > Hello, > > > > I can give a presentation about the pliant programming > language. > > > > BORIS > > > > Sent from my iPhone > > > > On Jan 29, 2009, at 10:39 PM, "john_re" > wrote: > > > > > Hi Adam, & anyone interested in this :) > > > > > > I invite > > > 1) you to make a 5-10 min presentation about your project > to > > > the BerkeleyTIP-Global meeting, Jan 7 Saturday, via VOIP. > > > 2) All your groups memebers to join in the global BTIP > meeting via > > > VOIP. > > > > > > We are a monthly global (via VOIP) meeting about > GNU(Linux) & BSD & > > > all > > > free sw & culture, so your effort fits right in. :) > > > http://groups.google.com/group/BerkTIP > > > Click "join this group" on the page rhs to get on the > mailing list. > > > > > > I'll mention about your event on the 10-20 announcements I > send out > > > about BTIP, so that might get you some more exposure, & > perhaps > > > volunteers. :) > > > > > > > > > I'll pass it on to a UCB CS professor, who is interested > in education > > > related topics. :) > > > > > > Is there anyone in your group who might like to give a > short, 5-10 min > > > talk about what you all are doing? Maybe just before 12N > pacific > > > time = > > > < 3P Eastern? > > > > > > > > > > > > On Sun, 25 Jan 2009 19:24:20 -0500, "Kevin Mark" > > > said: > > >> > > >> Forward from a fellow FLOSS supporter: > > >> > > >> If you are in the NY-area and would like to help out with > the project > > >> described > > >> below, they are looking for volunteers. Help FLOSSIFY the > enormously > > >> popular > > >> book Digital Foundations. The event is being hosted Feb > 6-8 at the > > >> lovely > > >> Eyebeam with some Free as in Beer and Grub provided! > > >> > > >> ******************************************************* > > >> > > >> FLOSSIFY 1 : Digital Foundations > > > ... > > > > > >> Our first text book is the wonderful Digital Foundations > book > > >> produced > > >> by Michael Mandiberg and Xtine Burrough > > >> (http://digital-foundations.net/). Its a text book > designed to teach > > >> software by teaching design. The current toolset it uses > is the Adobe > > >> Creative Suite and we will convert these examples > entirely to using > > >> free > > >> software. > > >> > > >> FLOSSIFY 1 : Digital Foundations will focus on a fun 3 > day event at > > >> Eyebeam, NYC. Anyone is welcome to attend and some food > and beer > > >> will be > > >> provided. Come and meet some of your old geek friends, > make some new, > > >> and help make a step towards unshackling education from > proprietary > > >> software. > > ... > > _____________________________________________________________________________ > Hire expert Linux talent by posting jobs here :: > http://jobs.nylug.org > The nylug-talk mailing list is at nylug-talk at nylug.org > The list archive is at http://nylug.org/pipermail/nylug-talk > To subscribe or unsubscribe: > http://nylug.org/mailman/listinfo/nylug-talk > > > > _______________________________________________ > 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 sevmek at free.fr Mon Feb 2 17:39:29 2009 From: sevmek at free.fr (yannick) Date: Mon, 02 Feb 2009 18:39:29 +0100 Subject: [Ekiga-list] 30fps on Ekiga 3.0.2 with H264 enabled In-Reply-To: <24b40b2b0902020645m58baebaapc8fa2a8245a7f84a@mail.gmail.com> References: <24b40b2b0902020645m58baebaapc8fa2a8245a7f84a@mail.gmail.com> Message-ID: <1233596369.18030.6.camel@achille> Le lundi 02 f?vrier 2009 ? 20:15 +0530, chaitanya mehandru a ?crit : > Please suggest a solution for logitech camera. This can be stupid, what if you add more (~much more) light to the room you're in ? From mike at cchtml.com Mon Feb 2 18:32:37 2009 From: mike at cchtml.com (Michael Cronenworth) Date: Mon, 02 Feb 2009 12:32:37 -0600 Subject: [Ekiga-list] 30fps on Ekiga 3.0.2 with H264 enabled In-Reply-To: <24b40b2b0902020645m58baebaapc8fa2a8245a7f84a@mail.gmail.com> References: <24b40b2b0902020645m58baebaapc8fa2a8245a7f84a@mail.gmail.com> Message-ID: <49873C45.8040907@cchtml.com> -------- Original Message -------- Subject: [Ekiga-list] 30fps on Ekiga 3.0.2 with H264 enabled From: chaitanya mehandru To: ekiga-list at gnome.org Date: 02/02/2009 08:45 AM > Hi, > Is it possible to reach a frame rate of 30fps on Ekiga 3.0.2 with > H264 enabled on Ubuntu 8.04 ( kernel 2.6.24-23 )...? > > I am using the Logitech QuickCam for Notebooks Pro 2Mpixel camera. I > have observed a range of transmistted / received frame from 21/9 to > 26/46 with and average of 24/12 most of the time. If there is some way > of achieving a ratio of 30/30, please let me know. > > On wiki.ekiga.org , it is mentioned that using > setpwc tool, we can set the philips webcams to support 30fps. But this > is limited to philips webcam only..!! > > Please suggest a solution for logitech camera. First things first. The numbers you see are for TX and RX (transmitting and receiving). The first set of numbers are the TX values. This is the frame rate that you are sending. The second set are the RX values. You can only control the TX values. The RX values are dependent on the person you are calling. Secondly, webcams require *LOTS* of light to have high frame rates on their automatic settings. We're talking sun light's worth of light. However, you can adjust your webcam manually. Modern Logitech webcams use the uvcvideo kernel driver and therefore can use the libwebcam library for access to your webcam settings. I have created a GTK+ 2.x interface[1] to the libwebcam library. This will allow you to manually configure your webcam even in real-time during a call. You may also wish to visit the official Logitech website[2] for the library. [1] http://michael.cronenworth.com/2009/01/recreational-programming.html [2] http://www.quickcamteam.net/software/libwebcam From wayne.ye23 at gmail.com Mon Feb 2 19:59:44 2009 From: wayne.ye23 at gmail.com (Wayne Ye) Date: Mon, 2 Feb 2009 14:59:44 -0500 Subject: [Ekiga-list] text chat Message-ID: Hi all, I have some questions about the text chat in gnomemeeting(1.0.2) and openh323(major version 1 and minor version 13). In that version it has a userinput capability. The characters input by one user is transmitted through functions: SendUserInput -> SendUserInputIndicationString -> WriteControlPDU -> WritePDU -> TCP Write. And then OpalLineChannel::Write()-> WriteFrame? Is that right? Another question is: Is the text transferred using the audio channel? Because I did not find a unique text channel or userinput channel like audio, vedio channel and the WriteFrame function also contains audio choices. Thank you very much, Wayne -------------- next part -------------- An HTML attachment was scrubbed... URL: From Dirk.dorme at gmail.com Tue Feb 3 00:02:46 2009 From: Dirk.dorme at gmail.com (Dirk Dorme) Date: Tue, 3 Feb 2009 13:02:46 +1300 Subject: [Ekiga-list] Conference call: how to Message-ID: <7f72a0700902021602r6dd16357re1dd4bb66d8ec4f7@mail.gmail.com> It must have been answered over and over again, but I really do not have a clue on where to start. We, up to 30, would like to do conference calls. I thought it would be possible through ekiga. However, have no idea on where to start. Could someone point out on how to organize that? Can we use skype to call in, do we need the ekiga soft (so not for mac)...? A step by step guide would be awesome. Thanks in advance. -------------- next part -------------- An HTML attachment was scrubbed... URL: From razametal at gmail.com Tue Feb 3 01:42:05 2009 From: razametal at gmail.com (RazaMetaL | Only The Good Die Young) Date: Mon, 2 Feb 2009 20:42:05 -0500 Subject: [Ekiga-list] Conference call: how to In-Reply-To: <7f72a0700902021602r6dd16357re1dd4bb66d8ec4f7@mail.gmail.com> References: <7f72a0700902021602r6dd16357re1dd4bb66d8ec4f7@mail.gmail.com> Message-ID: On Mon, Feb 2, 2009 at 7:02 PM, Dirk Dorme wrote: > It must have been answered over and over again, but I really do not have a > clue on where to start. > > We, up to 30, would like to do conference calls. I thought it would be > possible through ekiga. However, have no idea on where to start. Could > someone point out on how to organize that? Can we use skype to call in, do > we need the ekiga soft (so not for mac)...? > A step by step guide would be awesome. > > Thanks in advance. > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > Ekiga can not make conference calls with more than two participants. You need a H.323 MCU to make the conference works. OpenMCU works fine, but only allows up to 5 participants. Best regards, -- Linux User: 255902 Please avoid sending me Word or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html From chinku.linux at gmail.com Tue Feb 3 05:21:36 2009 From: chinku.linux at gmail.com (chaitanya mehandru) Date: Tue, 3 Feb 2009 10:51:36 +0530 Subject: [Ekiga-list] 30fps on Ekiga 3.0.2 with H264 enabled In-Reply-To: <49873C45.8040907@cchtml.com> References: <24b40b2b0902020645m58baebaapc8fa2a8245a7f84a@mail.gmail.com> <49873C45.8040907@cchtml.com> Message-ID: <24b40b2b0902022121x76c2a72je4aa2dc57d3262bd@mail.gmail.com> Hi Michael, Thanks so much for your inputs. Thanks, Chaitanya On Tue, Feb 3, 2009 at 12:02 AM, Michael Cronenworth wrote: > -------- Original Message -------- > Subject: [Ekiga-list] 30fps on Ekiga 3.0.2 with H264 enabled > From: chaitanya mehandru > To: ekiga-list at gnome.org > Date: 02/02/2009 08:45 AM > > Hi, >> Is it possible to reach a frame rate of 30fps on Ekiga 3.0.2 with H264 >> enabled on Ubuntu 8.04 ( kernel 2.6.24-23 )...? >> I am using the Logitech QuickCam for Notebooks Pro 2Mpixel camera. I have >> observed a range of transmistted / received frame from 21/9 to 26/46 with >> and average of 24/12 most of the time. If there is some way of achieving a >> ratio of 30/30, please let me know. >> On wiki.ekiga.org , it is mentioned that using >> setpwc tool, we can set the philips webcams to support 30fps. But this is >> limited to philips webcam only..!! >> Please suggest a solution for logitech camera. >> > > > First things first. The numbers you see are for TX and RX (transmitting and > receiving). The first set of numbers are the TX values. This is the frame > rate that you are sending. The second set are the RX values. You can only > control the TX values. The RX values are dependent on the person you are > calling. > > Secondly, webcams require *LOTS* of light to have high frame rates on their > automatic settings. We're talking sun light's worth of light. However, you > can adjust your webcam manually. Modern Logitech webcams use the uvcvideo > kernel driver and therefore can use the libwebcam library for access to your > webcam settings. > > I have created a GTK+ 2.x interface[1] to the libwebcam library. This will > allow you to manually configure your webcam even in real-time during a call. > You may also wish to visit the official Logitech website[2] for the library. > > [1] http://michael.cronenworth.com/2009/01/recreational-programming.html > [2] http://www.quickcamteam.net/software/libwebcam > > _______________________________________________ > 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 Tue Feb 3 05:35:03 2009 From: sevmek at free.fr (yannick) Date: Tue, 03 Feb 2009 06:35:03 +0100 Subject: [Ekiga-list] Conference call: how to In-Reply-To: <7f72a0700902021602r6dd16357re1dd4bb66d8ec4f7@mail.gmail.com> References: <7f72a0700902021602r6dd16357re1dd4bb66d8ec4f7@mail.gmail.com> Message-ID: <1233639303.18030.11.camel@achille> Le mardi 03 f?vrier 2009 ? 13:02 +1300, Dirk Dorme a ?crit : > We, up to 30, would like to do conference calls. I thought it would be You can use the ekiga.net service (audio only): https://www.ekiga.net/index.php?page=services > possible through ekiga. However, have no idea on where to start. > Could someone point out on how to organize that? Can we use skype to > call in, do we need the ekiga soft (so not for mac)...? There is no compatibility with Skype. Skype is one of the most hidden protocol available today. Ekiga use only world wide standard protocols for VoIP (mainly SIP). You can use Ekiga for call in/call out: http://wiki.ekiga.org/index.php/Calling Best regards, Yannick From chinku.linux at gmail.com Tue Feb 3 06:24:14 2009 From: chinku.linux at gmail.com (chaitanya mehandru) Date: Tue, 3 Feb 2009 11:54:14 +0530 Subject: [Ekiga-list] [nylug-talk] assistance with free-ing educational text btg In-Reply-To: <1233596069.18030.2.camel@achille> References: <20090126002420.GA14315@horacrux> <1233286747.9138.1297537503@webmail.messagingengine.com> <1233568498.30917.1298002007@webmail.messagingengine.com> <24b40b2b0902020238h6a961bc7s6507fea18f2577a0@mail.gmail.com> <1233596069.18030.2.camel@achille> Message-ID: <24b40b2b0902022224g4281fb02tc88f2e5bf0df000e@mail.gmail.com> Hi,I am more than willing to document it on wiki whatever i have been doing to build E3 on KDE 8.04. I think i should do it without any request also[?]. Currently, ekiga is done on KDE but there is one error: Whenever i try to launch ekiga, i see a message 'No Protocol Specified' and this message keeps coming 3-4 times in a row whenever i try to launch ekiga 3.0.2 and at last i see a segmentation fault error. I do't know if somebody also saw the same I checked in /root/.gconf/apps/ekiga and i didnt see any protocols directory. All I see is: Codecs & Contacts directory. So i think there is something missing as part of the configuration. If somebody has any idea on how to get the protocols also enlisted,then ekiga wont terminate searching for protocols. Thanks, Chaitanya On Mon, Feb 2, 2009 at 11:04 PM, yannick wrote: > Le lundi 02 f?vrier 2009 ? 16:08 +0530, chaitanya mehandru a ?crit : > > Hi, I already joined the list and said 'Hi'. My name is Chaitanya > > Mehandru. I am currently half way through building ekiga 3 on kde > > 8.04. Some issues with the Makefiles to be resolved. Can we talk about > > this in advance..? I have build the opal and ptlib successfully. > > > > Hello, > > Will you be kind enough to document what you've done in our wiki? > -> http://wiki.ekiga.org/index.php/Main_Page > > I can grant you a full writable access to the wiki, and open a page for > this topic. > > Best regards, > Yannick > > > > > Thanks, > > Chaitanya Mehandru > > > > On Mon, Feb 2, 2009 at 3:24 PM, john_re wrote: > > Hi Boris :) > > > > Pliant looks interesting :) > > > > We at the BerkeleyTIP global monthly meeting are working > > toward having > > remote persons give talks for the meeting. We've already > > successfully > > used a VOIP conference server for several months, & have had > > attendees > > from NorthCarolina, Michigan, Washington State & Hawaii. > > > > This month we might have a talk about Ekiga 3 given from > > India. > > > > Where in the world are you? Do you have VOIP capability? > > > > I'd suggest you join the BTIP mailing list & say "Hi", & tell > > us your > > thoughts on what you could cover in your P talk. > > > > Maybe we could start with a 5 minute mini talk this Feb 7, > > just so we > > all can better get the feel of doing live talks. :) > > > > We don't yet have a procedure for showing slides, or live > > computer > > output, but that will come in time. > > > > I hope to hear from you on the BTIP list! :) > > > > > > > > On Sat, 31 Jan 2009 10:42:46 -0500, "Boris Reitman" > > said: > > > Hello, > > > > > > I can give a presentation about the pliant programming > > language. > > > > > > BORIS > > > > > > Sent from my iPhone > > > > > > On Jan 29, 2009, at 10:39 PM, "john_re" > > wrote: > > > > > > > Hi Adam, & anyone interested in this :) > > > > > > > > I invite > > > > 1) you to make a 5-10 min presentation about your project > > to > > > > the BerkeleyTIP-Global meeting, Jan 7 Saturday, via VOIP. > > > > 2) All your groups memebers to join in the global BTIP > > meeting via > > > > VOIP. > > > > > > > > We are a monthly global (via VOIP) meeting about > > GNU(Linux) & BSD & > > > > all > > > > free sw & culture, so your effort fits right in. :) > > > > http://groups.google.com/group/BerkTIP > > > > Click "join this group" on the page rhs to get on the > > mailing list. > > > > > > > > I'll mention about your event on the 10-20 announcements I > > send out > > > > about BTIP, so that might get you some more exposure, & > > perhaps > > > > volunteers. :) > > > > > > > > > > > > I'll pass it on to a UCB CS professor, who is interested > > in education > > > > related topics. :) > > > > > > > > Is there anyone in your group who might like to give a > > short, 5-10 min > > > > talk about what you all are doing? Maybe just before 12N > > pacific > > > > time = > > > > < 3P Eastern? > > > > > > > > > > > > > > > > On Sun, 25 Jan 2009 19:24:20 -0500, "Kevin Mark" > > > > said: > > > >> > > > >> Forward from a fellow FLOSS supporter: > > > >> > > > >> If you are in the NY-area and would like to help out with > > the project > > > >> described > > > >> below, they are looking for volunteers. Help FLOSSIFY the > > enormously > > > >> popular > > > >> book Digital Foundations. The event is being hosted Feb > > 6-8 at the > > > >> lovely > > > >> Eyebeam with some Free as in Beer and Grub provided! > > > >> > > > >> ******************************************************* > > > >> > > > >> FLOSSIFY 1 : Digital Foundations > > > > ... > > > > > > > >> Our first text book is the wonderful Digital Foundations > > book > > > >> produced > > > >> by Michael Mandiberg and Xtine Burrough > > > >> (http://digital-foundations.net/). Its a text book > > designed to teach > > > >> software by teaching design. The current toolset it uses > > is the Adobe > > > >> Creative Suite and we will convert these examples > > entirely to using > > > >> free > > > >> software. > > > >> > > > >> FLOSSIFY 1 : Digital Foundations will focus on a fun 3 > > day event at > > > >> Eyebeam, NYC. Anyone is welcome to attend and some food > > and beer > > > >> will be > > > >> provided. Come and meet some of your old geek friends, > > make some new, > > > >> and help make a step towards unshackling education from > > proprietary > > > >> software. > > > > ... > > > > > _____________________________________________________________________________ > > Hire expert Linux talent by posting jobs here :: > > http://jobs.nylug.org > > The nylug-talk mailing list is at nylug-talk at nylug.org > > The list archive is at http://nylug.org/pipermail/nylug-talk > > To subscribe or unsubscribe: > > http://nylug.org/mailman/listinfo/nylug-talk > > > > > > > > _______________________________________________ > > 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 > > _______________________________________________ > 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 -------------- A non-text attachment was scrubbed... Name: 330.gif Type: image/gif Size: 96 bytes Desc: not available URL: From Dirk.dorme at gmail.com Tue Feb 3 06:34:19 2009 From: Dirk.dorme at gmail.com (Dirk Dorme) Date: Tue, 3 Feb 2009 19:34:19 +1300 Subject: [Ekiga-list] Conference call: how to Message-ID: <7f72a0700902022234t3fcbb110pb7c8c73a313af3c9@mail.gmail.com> Thanks for the replies. So I can organize a private conference. Does anyone know of a good Mac SIP client? -------------- next part -------------- An HTML attachment was scrubbed... URL: From jpuydt at free.fr Tue Feb 3 07:41:08 2009 From: jpuydt at free.fr (Julien Puydt) Date: Tue, 03 Feb 2009 08:41:08 +0100 Subject: [Ekiga-list] Conference call: how to In-Reply-To: <7f72a0700902022234t3fcbb110pb7c8c73a313af3c9@mail.gmail.com> References: <7f72a0700902022234t3fcbb110pb7c8c73a313af3c9@mail.gmail.com> Message-ID: <4987F514.5090400@free.fr> Dirk Dorme a ?crit : > So I can organize a private conference. Does anyone know of a good Mac SIP > client? http://wiki.ekiga.org/index.php/Ekiga_Interoperability Snark on #ekiga From jpuydt at free.fr Tue Feb 3 07:45:09 2009 From: jpuydt at free.fr (Julien Puydt) Date: Tue, 03 Feb 2009 08:45:09 +0100 Subject: [Ekiga-list] [nylug-talk] assistance with free-ing educational text btg In-Reply-To: <24b40b2b0902022224g4281fb02tc88f2e5bf0df000e@mail.gmail.com> References: <20090126002420.GA14315@horacrux> <1233286747.9138.1297537503@webmail.messagingengine.com> <1233568498.30917.1298002007@webmail.messagingengine.com> <24b40b2b0902020238h6a961bc7s6507fea18f2577a0@mail.gmail.com> <1233596069.18030.2.camel@achille> <24b40b2b0902022224g4281fb02tc88f2e5bf0df000e@mail.gmail.com> Message-ID: <4987F605.5090606@free.fr> chaitanya mehandru a ?crit : > Hi,I am more than willing to document it on wiki whatever i have been doing > to build E3 on KDE 8.04. I think i should do it without any request also[?]. Ubuntu 8.04 should ship the packages... > Currently, ekiga is done on KDE but there is one error: > Whenever i try to launch ekiga, i see a message 'No Protocol > Specified' and this message keeps coming 3-4 times in a row whenever i try > to launch ekiga 3.0.2 and at last i see a segmentation fault error. I do't > know if somebody also saw the same Uuhh... that doesn't remind anything. Is the message only "No Protocol Specified" ? > I checked in /root/.gconf/apps/ekiga and i didnt see any protocols > directory. /root/ !? Are you running ekiga as *root* !? Do you have a look under the hood of your car while driving to? Snark on #ekiga From chinku.linux at gmail.com Tue Feb 3 07:52:16 2009 From: chinku.linux at gmail.com (chaitanya mehandru) Date: Tue, 3 Feb 2009 13:22:16 +0530 Subject: [Ekiga-list] [nylug-talk] assistance with free-ing educational text btg In-Reply-To: <4987F605.5090606@free.fr> References: <20090126002420.GA14315@horacrux> <1233286747.9138.1297537503@webmail.messagingengine.com> <1233568498.30917.1298002007@webmail.messagingengine.com> <24b40b2b0902020238h6a961bc7s6507fea18f2577a0@mail.gmail.com> <1233596069.18030.2.camel@achille> <24b40b2b0902022224g4281fb02tc88f2e5bf0df000e@mail.gmail.com> <4987F605.5090606@free.fr> Message-ID: <24b40b2b0902022352w22ae0940k1d12e46fcc720931@mail.gmail.com> yes the message is exactly as i told. It is repeatedly sending: 'No Protocol Specified' Message. I shud not run as root...? its ok if i dont look under my car and drive faster. On Tue, Feb 3, 2009 at 1:15 PM, Julien Puydt wrote: > chaitanya mehandru a ?crit : > >> Hi,I am more than willing to document it on wiki whatever i have been >> doing >> to build E3 on KDE 8.04. I think i should do it without any request >> also[?]. >> > > Ubuntu 8.04 should ship the packages... > > Currently, ekiga is done on KDE but there is one error: >> Whenever i try to launch ekiga, i see a message 'No Protocol >> Specified' and this message keeps coming 3-4 times in a row whenever i try >> to launch ekiga 3.0.2 and at last i see a segmentation fault error. I do't >> know if somebody also saw the same >> > > Uuhh... that doesn't remind anything. Is the message only "No Protocol > Specified" ? > > I checked in /root/.gconf/apps/ekiga and i didnt see any protocols >> directory. >> > > /root/ !? Are you running ekiga as *root* !? > > Do you have a look under the hood of your car while driving to? > > Snark on #ekiga > > _______________________________________________ > 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 john_re at fastmail.us Tue Feb 3 07:55:06 2009 From: john_re at fastmail.us (john_re) Date: Mon, 02 Feb 2009 23:55:06 -0800 Subject: [Ekiga-list] Ekiga.net VOIP conference server info Message-ID: <1233647706.3413.1298206689@webmail.messagingengine.com> Is there a web page or faq that lists the characteristics of the ekiga.net VOIP conference server? https://www.ekiga.net/index.php?page=services If not, will you please tell me: 1) Who owns it? 2) who manages it? 3) where is the hw? 4) what general & special purpose hw does it use? 5) what sw does it run? 6) what is its network connectivity? 6b) what is the maximum conference participants it can handle 6c) can it now, or will it in the future, handle video conferencing? 7) What issues should one be aware of in attempting to create a global conference? Ex: USA & India? 7b) to ensure acceptable quality from multi continents, what can be done? Including, network providers with good VOIP quality TOS? Thanks :) http://sites.google.com/site/berkeleytip/ http://groups.google.com/group/BerkTIPGlobal http://groups.google.com/group/BerkTIPGlobal/web/irc-voip From duncan.lithgow at gmail.com Tue Feb 3 10:18:35 2009 From: duncan.lithgow at gmail.com (Duncan Lithgow) Date: Tue, 3 Feb 2009 11:18:35 +0100 Subject: [Ekiga-list] Can't call a second number once started Message-ID: Once I've started Ekiga (3.0.1 on Ubuntu 9.04) I can call the first number without trouble. After that whatever contact I click on I end up calling the first dialled number again and again. I have to restart Ekiga to fix this. Anyone else seeing this problem? Should I file this as a bug? Duncan From duncan.lithgow at gmail.com Tue Feb 3 10:23:05 2009 From: duncan.lithgow at gmail.com (Duncan Lithgow) Date: Tue, 3 Feb 2009 11:23:05 +0100 Subject: [Ekiga-list] Ekiga.net VOIP conference server info In-Reply-To: <1233647706.3413.1298206689@webmail.messagingengine.com> References: <1233647706.3413.1298206689@webmail.messagingengine.com> Message-ID: 2009/2/3 john_re : > Is there a web page or faq that lists the characteristics of the > ekiga.net VOIP conference server? > https://www.ekiga.net/index.php?page=services > > If not, will you please tell me: > > 1) Who owns it? Damian Sandras and others, under a GPL license > 2) who manages it? Damian Sandras and others, under a GPL license > 3) where is the hw? It is not hardware specific. It is a piece of software. > 4) what general & special purpose hw does it use? see above > 5) what sw does it run? I don't understand the question. It is a piece of software. > 6) what is its network connectivity? Someone else can answer this on you can look on the website ot wikipedia > 6b) what is the maximum conference participants it can handle Someone else can answer this on you can look on the website ot wikipedia > 6c) can it now, or will it in the future, handle video conferencing? Someone else can answer this on you can look on the website ot wikipedia > 7) What issues should one be aware of in attempting to create a global > conference? Ex: USA & India? Someone else can answer this on you can look on the website ot wikipedia > 7b) to ensure acceptable quality from multi continents, what can be > done? Including, network providers with good VOIP quality TOS? Someone else can answer this on you can look on the website ot wikipedia Can someone fill in the gaps I've left and add corrections? Duncan From dsandras at seconix.com Tue Feb 3 11:09:01 2009 From: dsandras at seconix.com (Damien Sandras) Date: Tue, 03 Feb 2009 12:09:01 +0100 Subject: [Ekiga-list] Can't call a second number once started In-Reply-To: References: Message-ID: <1233659341.4244.42.camel@scorpion.multitel.be> Le mardi 03 f?vrier 2009 ? 11:18 +0100, Duncan Lithgow a ?crit : > Once I've started Ekiga (3.0.1 on Ubuntu 9.04) I can call the first > number without trouble. After that whatever contact I click on I end > up calling the first dialled number again and again. I have to restart > Ekiga to fix this. > > Anyone else seeing this problem? Should I file this as a bug? > I do not think there is a bug in Ekiga (it would be terrible if for everybody it was only possible to make one call without restarting Ekiga). It is most probably a NAT problem again. Can you post a -d 4 output to pastebin ? -- _ 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 duncan.lithgow at gmail.com Tue Feb 3 11:14:38 2009 From: duncan.lithgow at gmail.com (Duncan Lithgow) Date: Tue, 3 Feb 2009 12:14:38 +0100 Subject: [Ekiga-list] Can't call a second number once started In-Reply-To: <1233659341.4244.42.camel@scorpion.multitel.be> References: <1233659341.4244.42.camel@scorpion.multitel.be> Message-ID: 2009/2/3 Damien Sandras : > Can you post a -d 4 output to pastebin ? Sure, what's that? Duncan From sevmek at free.fr Tue Feb 3 17:15:17 2009 From: sevmek at free.fr (yannick) Date: Tue, 03 Feb 2009 18:15:17 +0100 Subject: [Ekiga-list] [nylug-talk] assistance with free-ing educational text btg In-Reply-To: <24b40b2b0902022224g4281fb02tc88f2e5bf0df000e@mail.gmail.com> References: <20090126002420.GA14315@horacrux> <1233286747.9138.1297537503@webmail.messagingengine.com> <1233568498.30917.1298002007@webmail.messagingengine.com> <24b40b2b0902020238h6a961bc7s6507fea18f2577a0@mail.gmail.com> <1233596069.18030.2.camel@achille> <24b40b2b0902022224g4281fb02tc88f2e5bf0df000e@mail.gmail.com> Message-ID: <1233681317.18030.17.camel@achille> Le mardi 03 f?vrier 2009 ? 11:54 +0530, chaitanya mehandru a ?crit : > Hi, I am more than willing to document it on wiki whatever i have been > doing to build E3 on KDE 8.04. I think i should do it without any > request also. Soon, an email will hit your mail box with ID and password for our wiki. Thank you. If you have any request for how to use the wiki, you can ask me in private. Best Regards, Yannick From Eugen.Dedu at pu-pm.univ-fcomte.fr Tue Feb 3 17:18:41 2009 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Tue, 03 Feb 2009 18:18:41 +0100 Subject: [Ekiga-list] Can't call a second number once started In-Reply-To: References: <1233659341.4244.42.camel@scorpion.multitel.be> Message-ID: <49887C71.5080608@pu-pm.univ-fcomte.fr> Duncan Lithgow wrote: > 2009/2/3 Damien Sandras : >> Can you post a -d 4 output to pastebin ? > Sure, what's that? > > Duncan > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > > http://wiki.ekiga.org/index.php/Debugging_Ekiga -- Eugen From sevmek at free.fr Tue Feb 3 17:38:54 2009 From: sevmek at free.fr (yannick) Date: Tue, 03 Feb 2009 18:38:54 +0100 Subject: [Ekiga-list] Ekiga.net VOIP conference server info In-Reply-To: <1233647706.3413.1298206689@webmail.messagingengine.com> References: <1233647706.3413.1298206689@webmail.messagingengine.com> Message-ID: <1233682734.18030.37.camel@achille> Le lundi 02 f?vrier 2009 ? 23:55 -0800, john_re a ?crit : > Is there a web page or faq that lists the characteristics of the > ekiga.net VOIP conference server? > https://www.ekiga.net/index.php?page=services > No. > If not, will you please tell me: > Seems all valid requests: > 1) Who owns it? Damien Sandras. Ever is some people do have account and administer the server, I guess it is mainly under Damien's responsibility. Damien? > 2) who manages it? Damien Sandras, Jan AKA TheBonsai > 3) where is the hw? In France... My own country. Hosting: http://www.easyneuf.fr/ > 4) what general & special purpose hw does it use? Nothing fancy, just regular hw for a server. I'm not sure to truly understand your point here... > 5) what sw does it run? The nice part: Running on GNU/Linux Kamailio http://www.kamailio.org/ Asterisk http://www.asterisk.org/ + LAMP service -> dedicated user interface in PHP under GPL http://webxser.tuxfamily.org/ I'm currently working on a new user interface using Drupal http://drupal.org/ In short: The whole software stack is open source. > 6) what is its network connectivity? I do not know how much exactly. > 6b) what is the maximum conference participants it can handle I've no clue. I personally tested up to something like 10. > 6c) can it now, or will it in the future, handle video conferencing? Jan? Damien? > 7) What issues should one be aware of in attempting to create a global > conference? Ex: USA & India? It is numeric communication. Thus geographical mesures need to be reconsidered. It mostly depends on the underlying net infrastructure. I do not know Ekiga.net's own limits in this regard. > 7b) to ensure acceptable quality from multi continents, what can be > done? Including, network providers with good VOIP quality TOS? Are you considering professional use of the service? > > Thanks :) Hope that helps. Yannick > > http://sites.google.com/site/berkeleytip/ > http://groups.google.com/group/BerkTIPGlobal > http://groups.google.com/group/BerkTIPGlobal/web/irc-voip > _______________________________________________ > 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 sevmek at free.fr Tue Feb 3 17:40:00 2009 From: sevmek at free.fr (yannick) Date: Tue, 03 Feb 2009 18:40:00 +0100 Subject: [Ekiga-list] [nylug-talk] assistance with free-ing educational text btg In-Reply-To: <1233681317.18030.17.camel@achille> References: <20090126002420.GA14315@horacrux> <1233286747.9138.1297537503@webmail.messagingengine.com> <1233568498.30917.1298002007@webmail.messagingengine.com> <24b40b2b0902020238h6a961bc7s6507fea18f2577a0@mail.gmail.com> <1233596069.18030.2.camel@achille> <24b40b2b0902022224g4281fb02tc88f2e5bf0df000e@mail.gmail.com> <1233681317.18030.17.camel@achille> Message-ID: <1233682800.18030.39.camel@achille> The page to edit is here: http://wiki.ekiga.org/index.php/Compile_your_own_stable_Ekiga_version_3_on_Kubuntu_8.04 Yannick Le mardi 03 f?vrier 2009 ? 18:15 +0100, yannick a ?crit : > Le mardi 03 f?vrier 2009 ? 11:54 +0530, chaitanya mehandru a ?crit : > > Hi, I am more than willing to document it on wiki whatever i have been > > doing to build E3 on KDE 8.04. I think i should do it without any > > request also. > > Soon, an email will hit your mail box with ID and password for our wiki. > > Thank you. > > If you have any request for how to use the wiki, you can ask me in > private. > > 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 dsandras at seconix.com Tue Feb 3 18:40:08 2009 From: dsandras at seconix.com (Damien Sandras) Date: Tue, 03 Feb 2009 19:40:08 +0100 Subject: [Ekiga-list] Ekiga.net VOIP conference server info In-Reply-To: <1233682734.18030.37.camel@achille> References: <1233647706.3413.1298206689@webmail.messagingengine.com> <1233682734.18030.37.camel@achille> Message-ID: <1233686408.5192.1.camel@scorpion.multitel.be> Le mardi 03 f?vrier 2009 ? 18:38 +0100, yannick a ?crit : > Le lundi 02 f?vrier 2009 ? 23:55 -0800, john_re a ?crit : > > Is there a web page or faq that lists the characteristics of the > > ekiga.net VOIP conference server? > > https://www.ekiga.net/index.php?page=services > > > > No. > > > If not, will you please tell me: > > > > Seems all valid requests: > > > 1) Who owns it? > > Damien Sandras. Ever is some people do have account and administer the > server, I guess it is mainly under Damien's responsibility. Damien? I don't really own it. It is kindly hosted by easyneuf : http://easyneuf.fr > > 2) who manages it? > > Damien Sandras, Jan AKA TheBonsai Mainly Jan nowadays. > > 3) where is the hw? > > In France... My own country. > Hosting: http://www.easyneuf.fr/ > > > 4) what general & special purpose hw does it use? > > Nothing fancy, just regular hw for a server. I'm not sure to truly > understand your point here... > > > 5) what sw does it run? > > The nice part: > Running on GNU/Linux > Kamailio http://www.kamailio.org/ > Asterisk http://www.asterisk.org/ > + LAMP service > -> dedicated user interface in PHP under GPL > http://webxser.tuxfamily.org/ > > I'm currently working on a new user interface using Drupal > http://drupal.org/ > > In short: > The whole software stack is open source. > > > 6) what is its network connectivity? > > I do not know how much exactly. > > > 6b) what is the maximum conference participants it can handle > > I've no clue. I personally tested up to something like 10. > > > 6c) can it now, or will it in the future, handle video conferencing? > > Jan? Damien? In the future probably, we had tested in the past an asterisk app supporting video but we did not deploy it. > > > 7) What issues should one be aware of in attempting to create a global > > conference? Ex: USA & India? > > It is numeric communication. Thus geographical mesures need to be > reconsidered. It mostly depends on the underlying net infrastructure. > > I do not know Ekiga.net's own limits in this regard. > > > 7b) to ensure acceptable quality from multi continents, what can be > > done? Including, network providers with good VOIP quality TOS? > > Are you considering professional use of the service? > > > > Thanks :) > > Hope that helps. > > Yannick > > > > > http://sites.google.com/site/berkeleytip/ > > http://groups.google.com/group/BerkTIPGlobal > > http://groups.google.com/group/BerkTIPGlobal/web/irc-voip > > _______________________________________________ > > 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 > > _______________________________________________ > 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 zxxxt at yahoo.com Wed Feb 4 08:25:37 2009 From: zxxxt at yahoo.com (ZXT) Date: Wed, 4 Feb 2009 00:25:37 -0800 (PST) Subject: [Ekiga-list] Ekiga errors using Onesuite and Ekiga account In-Reply-To: <21721344.post@talk.nabble.com> References: <21721344.post@talk.nabble.com> Message-ID: <21826246.post@talk.nabble.com> ZXT wrote: > > When I launched the Ekiga application it register without a problem then I > added http://www.onesuite.com/products_Broadband_Main.asp OneSuite sip > account . It says "Service Unavailable". > > I restart the Ekiga application and now both SIP accounts has an error. > > Ekiga.net - Could not register (Illegal status code) > Onesuite - Could not register (Service unavailable) > > Screenshot of Error messages -> > http://www.nabble.com/file/p21721344/ekiga.JPG ekiga.JPG > > Anybody got an idea? > Just bumping my question. Again I'm getting error on both Onesuite and Ekiga account. Please check screenshot. Thanks. Z -- View this message in context: http://www.nabble.com/Ekiga-errors-using-Onesuite-and-Ekiga-account-tp21721344p21826246.html Sent from the Ekiga General mailing list archive at Nabble.com. From chinku.linux at gmail.com Wed Feb 4 08:49:09 2009 From: chinku.linux at gmail.com (chaitanya mehandru) Date: Wed, 4 Feb 2009 14:19:09 +0530 Subject: [Ekiga-list] E3 errors on Kde 8.04 Message-ID: <24b40b2b0902040049o114af290i9de03bb071586c84@mail.gmail.com> Hi, I have captured the errors after building E3 on KDE 8.04. It seems like ekiga is looking for X display and can't find it. We need to make it search for KDE display. Whenever I try to launch ekiga, or run the daemon 'Kded', I get the same error as 'No Protocol Specified'. Can anybody help me removing these errors or any suggestions? Thanks, Chaitanya -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- cannot open display: Run 'ekiga --help' to see a full list of available command line options. -------------- next part -------------- ================ Final configuration =================== Installing into prefix : /usr/local 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 OS Type : linux-gnu Machine Type : i686 Byte Order : little endian -------------- next part -------------- No protocol specified No protocol specified No protocol specified No protocol specified (ekiga:5538): GLib-GObject-WARNING **: invalid (NULL) pointer instance (ekiga:5538): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed (ekiga:5538): Gtk-CRITICAL **: gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed (ekiga:5538): GLib-GObject-CRITICAL **: g_object_get: assertion `G_IS_OBJECT (object)' failed (ekiga:5538): GLib-GObject-WARNING **: value "TRUE" of type `gboolean' is invalid or out of range for property `visible' of type `gboolean' (ekiga:5538): Gtk-CRITICAL **: gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed (ekiga:5538): GLib-GObject-CRITICAL **: g_object_get: assertion `G_IS_OBJECT (object)' failed (ekiga:5538): Gtk-CRITICAL **: gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed (ekiga:5538): GLib-GObject-CRITICAL **: g_object_get: assertion `G_IS_OBJECT (object)' failed (ekiga:5538): Gtk-CRITICAL **: gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed (ekiga:5538): GLib-GObject-CRITICAL **: g_object_get: assertion `G_IS_OBJECT (object)' failed (ekiga:5538): GLib-GObject-WARNING **: invalid (NULL) pointer instance (ekiga:5538): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed (ekiga:5538): Gtk-CRITICAL **: gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed (ekiga:5538): GLib-GObject-CRITICAL **: g_object_get: assertion `G_IS_OBJECT (object)' failed (ekiga:5538): Gtk-CRITICAL **: gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed (ekiga:5538): GLib-GObject-CRITICAL **: g_object_get: assertion `G_IS_OBJECT (object)' failed (ekiga:5538): GLib-GObject-WARNING **: value "TRUE" of type `gboolean' is invalid or out of range for property `visible' of type `gboolean' (ekiga:5538): Gtk-CRITICAL **: gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed (ekiga:5538): GLib-GObject-CRITICAL **: g_object_get: assertion `G_IS_OBJECT (object)' failed (ekiga:5538): Gtk-CRITICAL **: gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed (ekiga:5538): GLib-GObject-CRITICAL **: g_object_get: assertion `G_IS_OBJECT (object)' failed (ekiga:5538): Gtk-CRITICAL **: gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed (ekiga:5538): GLib-GObject-CRITICAL **: g_object_get: assertion `G_IS_OBJECT (object)' failed (ekiga:5538): Gtk-CRITICAL **: gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed (ekiga:5538): GLib-GObject-CRITICAL **: g_object_get: assertion `G_IS_OBJECT (object)' failed (ekiga:5538): Gtk-CRITICAL **: gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed (ekiga:5538): GLib-GObject-CRITICAL **: g_object_get: assertion `G_IS_OBJECT (object)' failed (ekiga:5538): Gtk-CRITICAL **: gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed (ekiga:5538): GLib-GObject-CRITICAL **: g_object_get: assertion `G_IS_OBJECT (object)' failed (ekiga:5538): Gtk-CRITICAL **: gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed (ekiga:5538): GLib-GObject-CRITICAL **: g_object_get: assertion `G_IS_OBJECT (object)' failed (ekiga:5538): Gtk-CRITICAL **: gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed (ekiga:5538): GLib-GObject-CRITICAL **: g_object_get: assertion `G_IS_OBJECT (object)' failed (ekiga:5538): Gtk-CRITICAL **: gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed (ekiga:5538): GLib-GObject-CRITICAL **: g_object_get: assertion `G_IS_OBJECT (object)' failed (ekiga:5538): Gtk-CRITICAL **: gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed (ekiga:5538): GLib-GObject-CRITICAL **: g_object_get: assertion `G_IS_OBJECT (object)' failed (ekiga:5538): Gtk-CRITICAL **: gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed (ekiga:5538): GLib-GObject-CRITICAL **: g_object_get: assertion `G_IS_OBJECT (object)' failed (ekiga:5538): Gtk-CRITICAL **: gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed (ekiga:5538): GLib-GObject-CRITICAL **: g_object_get: assertion `G_IS_OBJECT (object)' failed (ekiga:5538): Gtk-CRITICAL **: gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed (ekiga:5538): GLib-GObject-CRITICAL **: g_object_get: assertion `G_IS_OBJECT (object)' failed (ekiga:5538): Gtk-CRITICAL **: gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed (ekiga:5538): GLib-GObject-CRITICAL **: g_object_get: assertion `G_IS_OBJECT (object)' failed (ekiga:5538): Gtk-CRITICAL **: gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed (ekiga:5538): GLib-GObject-CRITICAL **: g_object_get: assertion `G_IS_OBJECT (object)' failed (ekiga:5538): Gtk-CRITICAL **: gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed (ekiga:5538): GLib-GObject-CRITICAL **: g_object_get: assertion `G_IS_OBJECT (object)' failed (ekiga:5538): Gtk-CRITICAL **: gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed (ekiga:5538): GLib-GObject-CRITICAL **: g_object_get: assertion `G_IS_OBJECT (object)' failed (ekiga:5538): Gtk-CRITICAL **: gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed (ekiga:5538): GLib-GObject-WARNING **: invalid (NULL) pointer instance (ekiga:5538): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed -------------- next part -------------- root at lubov:/etc/kde3# ekiga& [1] 26473 root at lubov:/etc/kde3# No protocol specified cannot open display: Run 'ekiga --help' to see a full list of available command line options. [1]+ Exit 1 ekiga root at lubov:/etc/kde3# kded No protocol specified kded: cannot connect to X server :0.0 kded: ERROR: KUniqueApplication: Registering failed! kded: ERROR: Communication problem with kded, it probably crashed. root at lubov:/etc/kde3# kdostartupconfig root at lubov:/etc/kde3# kde-menu No protocol specified kde-menu: cannot connect to X server :0.0 -------------- next part -------------- No protocol specified No protocol specified No protocol specified No protocol specified (ekiga:5538): GLib-GObject-WARNING **: invalid (NULL) pointer instance (ekiga:5538): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed (ekiga:5538): Gtk-CRITICAL **: gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed (ekiga:5538): GLib-GObject-CRITICAL **: g_object_get: assertion `G_IS_OBJECT (object)' failed (ekiga:5538): GLib-GObject-WARNING **: value "TRUE" of type `gboolean' is invalid or out of range for property `visible' of type `gboolean' (ekiga:5538): Gtk-CRITICAL **: gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed (ekiga:5538): GLib-GObject-CRITICAL **: g_object_get: assertion `G_IS_OBJECT (object)' failed (ekiga:5538): Gtk-CRITICAL **: gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed (ekiga:5538): GLib-GObject-CRITICAL **: g_object_get: assertion `G_IS_OBJECT (object)' failed (ekiga:5538): Gtk-CRITICAL **: gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed (ekiga:5538): GLib-GObject-CRITICAL **: g_object_get: assertion `G_IS_OBJECT (object)' failed (ekiga:5538): GLib-GObject-WARNING **: invalid (NULL) pointer instance (ekiga:5538): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed (ekiga:5538): Gtk-CRITICAL **: gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed (ekiga:5538): GLib-GObject-CRITICAL **: g_object_get: assertion `G_IS_OBJECT (object)' failed (ekiga:5538): Gtk-CRITICAL **: gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed (ekiga:5538): GLib-GObject-CRITICAL **: g_object_get: assertion `G_IS_OBJECT (object)' failed (ekiga:5538): GLib-GObject-WARNING **: value "TRUE" of type `gboolean' is invalid or out of range for property `visible' of type `gboolean' (ekiga:5538): Gtk-CRITICAL **: gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed (ekiga:5538): GLib-GObject-CRITICAL **: g_object_get: assertion `G_IS_OBJECT (object)' failed (ekiga:5538): Gtk-CRITICAL **: gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed (ekiga:5538): GLib-GObject-CRITICAL **: g_object_get: assertion `G_IS_OBJECT (object)' failed (ekiga:5538): Gtk-CRITICAL **: gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed (ekiga:5538): GLib-GObject-CRITICAL **: g_object_get: assertion `G_IS_OBJECT (object)' failed (ekiga:5538): Gtk-CRITICAL **: gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed (ekiga:5538): GLib-GObject-CRITICAL **: g_object_get: assertion `G_IS_OBJECT (object)' failed (ekiga:5538): Gtk-CRITICAL **: gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed (ekiga:5538): GLib-GObject-CRITICAL **: g_object_get: assertion `G_IS_OBJECT (object)' failed (ekiga:5538): Gtk-CRITICAL **: gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed (ekiga:5538): GLib-GObject-CRITICAL **: g_object_get: assertion `G_IS_OBJECT (object)' failed (ekiga:5538): Gtk-CRITICAL **: gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed (ekiga:5538): GLib-GObject-CRITICAL **: g_object_get: assertion `G_IS_OBJECT (object)' failed (ekiga:5538): Gtk-CRITICAL **: gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed (ekiga:5538): GLib-GObject-CRITICAL **: g_object_get: assertion `G_IS_OBJECT (object)' failed (ekiga:5538): Gtk-CRITICAL **: gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed (ekiga:5538): GLib-GObject-CRITICAL **: g_object_get: assertion `G_IS_OBJECT (object)' failed (ekiga:5538): Gtk-CRITICAL **: gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed (ekiga:5538): GLib-GObject-CRITICAL **: g_object_get: assertion `G_IS_OBJECT (object)' failed (ekiga:5538): Gtk-CRITICAL **: gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed (ekiga:5538): GLib-GObject-CRITICAL **: g_object_get: assertion `G_IS_OBJECT (object)' failed (ekiga:5538): Gtk-CRITICAL **: gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed (ekiga:5538): GLib-GObject-CRITICAL **: g_object_get: assertion `G_IS_OBJECT (object)' failed (ekiga:5538): Gtk-CRITICAL **: gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed (ekiga:5538): GLib-GObject-CRITICAL **: g_object_get: assertion `G_IS_OBJECT (object)' failed (ekiga:5538): Gtk-CRITICAL **: gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed (ekiga:5538): GLib-GObject-CRITICAL **: g_object_get: assertion `G_IS_OBJECT (object)' failed (ekiga:5538): Gtk-CRITICAL **: gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed (ekiga:5538): GLib-GObject-CRITICAL **: g_object_get: assertion `G_IS_OBJECT (object)' failed (ekiga:5538): Gtk-CRITICAL **: gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed (ekiga:5538): GLib-GObject-CRITICAL **: g_object_get: assertion `G_IS_OBJECT (object)' failed (ekiga:5538): Gtk-CRITICAL **: gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed (ekiga:5538): GLib-GObject-CRITICAL **: g_object_get: assertion `G_IS_OBJECT (object)' failed (ekiga:5538): Gtk-CRITICAL **: gtk_settings_get_for_screen: assertion `GDK_IS_SCREEN (screen)' failed (ekiga:5538): GLib-GObject-WARNING **: invalid (NULL) pointer instance (ekiga:5538): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed From john_re at fastmail.us Wed Feb 4 09:24:04 2009 From: john_re at fastmail.us (john_re) Date: Wed, 04 Feb 2009 01:24:04 -0800 Subject: [Ekiga-list] Kubuntu, KDE, non root was- Re: E3 errors on Kde 8.04 In-Reply-To: <24b40b2b0902040049o114af290i9de03bb071586c84@mail.gmail.com> References: <24b40b2b0902040049o114af290i9de03bb071586c84@mail.gmail.com> Message-ID: <1233739444.12480.1298442323@webmail.messagingengine.com> 1) also ask on the KUbuntu, & KDE developers lists, 2) have you tried running this as user, not root? I have some old vague memory about some gui settings not being available under root, but are as regular user, on KDE or KUbuntu. On Wed, 4 Feb 2009 14:19:09 +0530, "chaitanya mehandru" said: > Hi, I have captured the errors after building E3 on KDE 8.04. It seems > like ekiga is looking for X display and can't find it. We need to make it > search for KDE display. > > Whenever I try to launch ekiga, or run the daemon 'Kded', I get the same > error as 'No Protocol Specified'. > > Can anybody help me removing these errors or any suggestions? > > Thanks, > Chaitanya From chinku.linux at gmail.com Wed Feb 4 09:31:29 2009 From: chinku.linux at gmail.com (chaitanya mehandru) Date: Wed, 4 Feb 2009 15:01:29 +0530 Subject: [Ekiga-list] Kubuntu, KDE, non root was- Re: E3 errors on Kde 8.04 In-Reply-To: <1233739444.12480.1298442323@webmail.messagingengine.com> References: <24b40b2b0902040049o114af290i9de03bb071586c84@mail.gmail.com> <1233739444.12480.1298442323@webmail.messagingengine.com> Message-ID: <24b40b2b0902040131k4d2e4b10n5a12ecb6b01a31e@mail.gmail.com> Hey John, You are awesome......Now i have ekiga running on KDE 8.04. Why couldn't I think of being regular user. So, now as I am done, I will move towards documenting every step taken in bringing ekiga up on KDE 8.04. Thanks, Chaitanya On Wed, Feb 4, 2009 at 2:54 PM, john_re wrote: > 1) also ask on the KUbuntu, & KDE developers lists, > 2) have you tried running this as user, not root? I have some old vague > memory about some gui settings not being available under root, but are > as regular user, on KDE or KUbuntu. > > On Wed, 4 Feb 2009 14:19:09 +0530, "chaitanya mehandru" > said: > > Hi, I have captured the errors after building E3 on KDE 8.04. It seems > > like ekiga is looking for X display and can't find it. We need to make it > > search for KDE display. > > > > Whenever I try to launch ekiga, or run the daemon 'Kded', I get the same > > error as 'No Protocol Specified'. > > > > Can anybody help me removing these errors or any suggestions? > > > > Thanks, > > Chaitanya > _______________________________________________ > 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 john_re at fastmail.us Wed Feb 4 09:55:47 2009 From: john_re at fastmail.us (john_re) Date: Wed, 04 Feb 2009 01:55:47 -0800 Subject: [Ekiga-list] Ekiga.net VOIP conference server info In-Reply-To: <1233686408.5192.1.camel@scorpion.multitel.be> References: <1233647706.3413.1298206689@webmail.messagingengine.com> <1233682734.18030.37.camel@achille> <1233686408.5192.1.camel@scorpion.multitel.be> Message-ID: <1233741347.19079.1298445445@webmail.messagingengine.com> On Tue, 03 Feb 2009 19:40:08 +0100, "Damien Sandras" said: > Le mardi 03 f?vrier 2009 ? 18:38 +0100, yannick a ?crit : > > Le lundi 02 f?vrier 2009 ? 23:55 -0800, john_re a ?crit : > > > Is there a web page or faq that lists the characteristics of the > > > ekiga.net VOIP conference server? > > https://www.ekiga.net/index.php?page=services .> > > If not, will you please tell me: > > > 1) Who owns it? > > > > Damien Sandras. Ever is some people do have account and administer the > > server, I guess it is mainly under Damien's responsibility. Damien? > > I don't really own it. It is kindly hosted by easyneuf : > http://easyneuf.fr > > > > 2) who manages it? > > > > Damien Sandras, Jan AKA TheBonsai > > Mainly Jan nowadays. > > > > 3) where is the hw? > > > > In France... My own country. > > Hosting: http://www.easyneuf.fr/ > > > > > 4) what general & special purpose hw does it use? > > > > Nothing fancy, just regular hw for a server. I'm not sure to truly > > understand your point here... Point: Is there any VOIP specific hardware? Maybe some telecom carrier grade voice IO capability stuff? Low latency throughput, etc? Maybe some Digium stuff?? > > > > > 5) what sw does it run? > > > > The nice part: > > Running on GNU/Linux > > Kamailio http://www.kamailio.org/ > > Asterisk http://www.asterisk.org/ > > + LAMP service > > -> dedicated user interface in PHP under GPL > > http://webxser.tuxfamily.org/ > > > > I'm currently working on a new user interface using Drupal > > http://drupal.org/ > > > > In short: > > The whole software stack is open source. > > Mostly I'm interested in the sw that does the voip conferencing, that mixes the audio stream. & also control for the conference room - is there, or can there be made available, easily, some control panel for a voip conference, that shows status info about the conference members, the rate & quality of their connections, etc - something to help manage a conference to any useful extent, & perhaps debug connections, - like volume levels, etc Like, we did some conferences using it, & sometimes some people seemed too loud, or maybe had background noise, (music, keyboard clicks), & it would be nice to have tools for the meeting manager to identify problems (ex- which line has the music playing, so we could turn down the volume on that channel, cause they went away from their computer & forgot to turn their mic off, etc) > > > 6) what is its network connectivity? > > > > I do not know how much exactly. Anyone? Can we get info from Jan AKA TheBonsai? Multiple peering? Data rate? Mere internet, or voice carrier connections? > > > > > 6b) what is the maximum conference participants it can handle > > > > I've no clue. I personally tested up to something like 10. > > Jan? > > > 6c) can it now, or will it in the future, handle video conferencing? > > > > Jan? Damien? > > In the future probably, we had tested in the past an asterisk app > supporting video but we did not deploy it. > > > > > > 7) What issues should one be aware of in attempting to create a global > > > conference? Ex: USA & India? > > > > It is numeric communication. Thus geographical mesures need to be > > reconsidered. It mostly depends on the underlying net infrastructure. > > > > I do not know Ekiga.net's own limits in this regard. > > Jan? anyone? > > > 7b) to ensure acceptable quality from multi continents, what can be > > > done? Including, network providers with good VOIP quality TOS? > > > > Are you considering professional use of the service? No, just for the BerkeleyTIP monthly meeting. http://sites.google.com/site/berkeleytip/ > > > > > > Thanks :) > > > > Hope that helps. > > > > Yannick Thanks :) > > > > > > > > http://sites.google.com/site/berkeleytip/ > > > http://groups.google.com/group/BerkTIPGlobal > > > http://groups.google.com/group/BerkTIPGlobal/web/irc-voip From john_re at fastmail.us Wed Feb 4 11:01:09 2009 From: john_re at fastmail.us (john_re) Date: Wed, 04 Feb 2009 03:01:09 -0800 Subject: [Ekiga-list] Kubuntu, KDE, non root was- Re: E3 errors on Kde 8.04 In-Reply-To: <24b40b2b0902040131k4d2e4b10n5a12ecb6b01a31e@mail.gmail.com> References: <24b40b2b0902040049o114af290i9de03bb071586c84@mail.gmail.com> <1233739444.12480.1298442323@webmail.messagingengine.com> <24b40b2b0902040131k4d2e4b10n5a12ecb6b01a31e@mail.gmail.com> Message-ID: <1233745269.31642.1298456031@webmail.messagingengine.com> Great :) Thanks for all your work. Have you tested it out for the loopback & conference room at ekiga.net & 1 on 1 communication? On Wed, 4 Feb 2009 15:01:29 +0530, "chaitanya mehandru" said: > Hey John, You are awesome......Now i have ekiga running on > KDE > 8.04. Why couldn't I think of being regular user. > So, now as I am done, I will move towards documenting every step taken in > bringing ekiga up on KDE 8.04. > > Thanks, > Chaitanya > > On Wed, Feb 4, 2009 at 2:54 PM, john_re wrote: > > > 1) also ask on the KUbuntu, & KDE developers lists, > > 2) have you tried running this as user, not root? I have some old vague > > memory about some gui settings not being available under root, but are > > as regular user, on KDE or KUbuntu. > > > > On Wed, 4 Feb 2009 14:19:09 +0530, "chaitanya mehandru" > > said: > > > Hi, I have captured the errors after building E3 on KDE 8.04. It seems > > > like ekiga is looking for X display and can't find it. We need to make it > > > search for KDE display. > > > > > > Whenever I try to launch ekiga, or run the daemon 'Kded', I get the same > > > error as 'No Protocol Specified'. > > > > > > Can anybody help me removing these errors or any suggestions? > > > > > > Thanks, > > > Chaitanya > > _______________________________________________ > > ekiga-list mailing list > > ekiga-list at gnome.org > > http://mail.gnome.org/mailman/listinfo/ekiga-list > > From chinku.linux at gmail.com Wed Feb 4 11:10:31 2009 From: chinku.linux at gmail.com (chaitanya mehandru) Date: Wed, 4 Feb 2009 16:40:31 +0530 Subject: [Ekiga-list] Kubuntu, KDE, non root was- Re: E3 errors on Kde 8.04 In-Reply-To: <1233745269.31642.1298456031@webmail.messagingengine.com> References: <24b40b2b0902040049o114af290i9de03bb071586c84@mail.gmail.com> <1233739444.12480.1298442323@webmail.messagingengine.com> <24b40b2b0902040131k4d2e4b10n5a12ecb6b01a31e@mail.gmail.com> <1233745269.31642.1298456031@webmail.messagingengine.com> Message-ID: <24b40b2b0902040310s7220fa8aqb695d9c8f52edd6f@mail.gmail.com> I got busy with some other stuff at work. Please allow me some time and I can check for the loopback test and 1 on 1 comunication as well. On Wed, Feb 4, 2009 at 4:31 PM, john_re wrote: > Great :) Thanks for all your work. > Have you tested it out for the loopback & conference room at ekiga.net & > 1 on 1 communication? > > On Wed, 4 Feb 2009 15:01:29 +0530, "chaitanya mehandru" > said: > > Hey John, You are awesome......Now i have ekiga running on > > KDE > > 8.04. Why couldn't I think of being regular user. > > So, now as I am done, I will move towards documenting every step taken in > > bringing ekiga up on KDE 8.04. > > > > Thanks, > > Chaitanya > > > > On Wed, Feb 4, 2009 at 2:54 PM, john_re wrote: > > > > > 1) also ask on the KUbuntu, & KDE developers lists, > > > 2) have you tried running this as user, not root? I have some old > vague > > > memory about some gui settings not being available under root, but are > > > as regular user, on KDE or KUbuntu. > > > > > > On Wed, 4 Feb 2009 14:19:09 +0530, "chaitanya mehandru" > > > said: > > > > Hi, I have captured the errors after building E3 on KDE 8.04. It > seems > > > > like ekiga is looking for X display and can't find it. We need to > make it > > > > search for KDE display. > > > > > > > > Whenever I try to launch ekiga, or run the daemon 'Kded', I get the > same > > > > error as 'No Protocol Specified'. > > > > > > > > Can anybody help me removing these errors or any suggestions? > > > > > > > > Thanks, > > > > Chaitanya > > > _______________________________________________ > > > 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 john_re at fastmail.us Wed Feb 4 12:01:10 2009 From: john_re at fastmail.us (john_re) Date: Wed, 04 Feb 2009 04:01:10 -0800 Subject: [Ekiga-list] BerkeleyTIP Feb 7 Sat Global Meeting - Ekiga3, Asterisk, KDE, GPGPU, Debian Edu, GStreamer Message-ID: <1233748870.10945.1298464615@webmail.messagingengine.com> ** Great talks this meeting: (live & on video) ** Ekiga3, Asterisk, GPGPU, GStreamer, Debian Edu, HowTo Present KDE at meetings http://sites.google.com/site/berkeleytip/ Join from anywhere via VOIP conference, with the friendly, educational, productive, BerkeleyTIP people. :) Join the #berkeleytip freenode.net IRC channel for help getting your VOIP working. http://groups.google.com/group/BerkTIPGlobal/web/irc-voip Programming Party: Whatever you want to work on, or group VOIP technology. ===================================================================== ***** FEB 7 SCHEDULE (California PacificStandardTime = -8h GMT) ***** Time Activity & Talks ---- ------------------------------------- 10 A Setup. Installfest begin. IRC & VOIP online 11 Ekiga 3 VOIP HowTo - Live from India 12 N Asterisk Free Software Telephone System 1 P " 2 GPGPU - General Purpose computing w/ Graphics Processing Units 3 " 4 Debian Edu - 100% in main 5 ** 5 Minute Lightning Talks ** GStreamer Multimedia Framework 6 HowTo Rock the Show with KDE 630 - Cleanup [Adjust for your local time: 10AM - 6:30PM PST = 1PM - 9:30PM Eastern = 6PM - 2:30AM GMT] ----- Ekiga 3 VOIP HowTo Install - Chaitanya Mehandru - 1h Live - Most distros only have version 2 The Asterisk Free Software Telephone System - Paul Charles Leddy - 1h23m http://nylug.org/meetings/index.shtml?20081000 GPGPU - General Purpose GPUs - John Stone - 1h43m http://www.archive.org/details/clug-28-10-2008-gpu-computing Debian Edu 100% in main - Holger Levsen - 1h https://penta.debconf.org/dc8_schedule/events/286.en.html GStreamer Multimedia Framework - Richard Spiers - 42m http://www.archive.org/details/clug-30-09-2008-gstreamer How to rock the show with KDE - Lydia Pintscher - 30m http://akademy.kde.org/conference/presentation/42.php - "How to present the KDE project at a conference." ** Download the talk videos you want to see the day _before_ the meeting, so your internet connection is free to do VOIP, & not consumed with the video download. :) ===================================================================== ===== JOIN THE BERKELEY-TIP MAILING LIST Join the mailing list, say "Hi", & introduce yourself, or just follow the discussions. Click "Join this group" on the right side of the page: http://groups.google.com/group/BerkTIPGlobal ===================================================================== ===== BERKELEY-TIP - MONTHLY GNU(LINUX) BSD FREE SW HW CULTURE MEETING BerkeleyTIP is a great monthly meeting about GNU(Linux), BSD & all free SW HW & Culture. Come learn about, install, use & help produce some SW. :) http://sites.google.com/site/berkeleytip/ ===================================================================== ===== YOU GIVE A 5 MINUTE LIGHTNING TALK? Send an email to the group with the topic you want to talk about. We'll likely approve all talks about any of: GNU(Linux) BSD or any Free SW HW or Culture subject to time constraints. :) ===================================================================== ===== EDUCATIONAL OUTREACH - SPRING 2009 - COLLEGES & UNIVERSITIES Join our effort to bring the BerkeleyTIP monthly meetings to local in-person gatherings at Colleges & Universities everywhere. :) You are encouraged to do any of these you want to: 1) Organize a local meeting at a college or university. - A WIFI cafe, or classroom, is a great place to meet. :) 2) Invite attendees by email - you can forward, and add to, this email. 3) Put up meeting announcement posters where appropriate - - see the BTIP site for the current poster 8.5x11 inch ODF file. DO: Join the BTIP mailing list & let's discuss & share ideas about how to make this a success. :) ===================================================================== ===== RECORD YOUR LOCAL MEETINGS' TALKS It's easy. Bring a video camera, tripod, lapel pin microphone, & microphone cable. Or, just put your camera within about 5-10 feet from the speaker. Put your video online - the internet archive is a great place. Be sure to send me a link. :) I'll try to schedule all newly recorded videos into the next BerkeleyTIP meeting. :) ===================================================================== ===== FORWARD THIS ANNOUNCEMENT EMAIL WHERE APPROPRIATE You are invited to forward this email wherever appropriate. Pass the word on, encourage other people to attend the meeting, & encourage the growth, improvement & strengthening of all Public Property, Community, "Free as in Freedom & FreeSpeech" software. :) From leamas.alec at gmail.com Wed Feb 4 12:27:19 2009 From: leamas.alec at gmail.com (Alec Leamas) Date: Wed, 04 Feb 2009 13:27:19 +0100 Subject: [Ekiga-list] Visual feedback when doing ekiga -c calls Message-ID: <498989A7.5010803@gmail.com> As of now, if a running ekiga instance makes a call started through "ekiga -c #" there is no visual feedback at all. Somehow, when I use this, it creates a little uneasy feeling (despite the obvious audio feedback). Also, if I lose connection to my account (and thus can't receive or place calls), there is still the same green spot in the tray... Thinking about it, from a user perspective there is really four states: - "No dialtone" i.e., no registered account. - Idle, ready... - Connecting - Connected I think it would make sense to reflect all these states in the tray icon. Nothing like Skype, which throws up it's main window when a call is initiated - it just irritating when you work in another application. Maybe just change colour on the green spoot in the tray. Just to illustrate what I have in mind: - No dialtone: Red spot, tooltip "No account registered" - Idle: Green spot, tooltip "Diamondcard account registered" or "Two accounts registered" - Connecting: yellow spot, tooltip "Connecting to "1111111 at sip.provider.com" - Connected: as today, tooltip "Connected to "111111 at sip.provider.com" Or? --alec From sevmek at free.fr Wed Feb 4 12:59:19 2009 From: sevmek at free.fr (yannick) Date: Wed, 04 Feb 2009 13:59:19 +0100 Subject: [Ekiga-list] Visual feedback when doing ekiga -c calls In-Reply-To: <498989A7.5010803@gmail.com> References: <498989A7.5010803@gmail.com> Message-ID: <1233752359.18030.46.camel@achille> Le mercredi 04 f?vrier 2009 ? 13:27 +0100, Alec Leamas a ?crit : > As of now, if a running ekiga instance makes a call started through > "ekiga -c #" there is no visual feedback at all. Somehow, when I use > this, it creates a little uneasy feeling (despite the obvious audio > feedback). Also, if I lose connection to my account (and thus can't > receive or place calls), there is still the same green spot in the tray... > > Thinking about it, from a user perspective there is really four states: > > - "No dialtone" i.e., no registered account. > - Idle, ready... > - Connecting > - Connected > > I think it would make sense to reflect all these states in the tray > icon. Nothing like Skype, which throws up it's main window when a call > is initiated - it just irritating when you work in another application. > Maybe just change colour on the green spoot in the tray. Just to > illustrate what I have in mind: > > - No dialtone: Red spot, tooltip "No account registered" > - Idle: Green spot, tooltip "Diamondcard account registered" or "Two > accounts registered" > - Connecting: yellow spot, tooltip "Connecting to "1111111 at sip.provider.com" > - Connected: as today, tooltip "Connected to "111111 at sip.provider.com" > > Or? There is maybe a place for that in the main GUI rather than in the systray (the systray reflect your status already, mixing both status and connectivity will be overkill). I'm thinking about the quality meter at the bottom. It is always visible and except when you're in a call, it is pretty useless. No dialtone, idle and connecting can fill this useless, while connected would be where the quality info will be shown. Regards, Yannick From leamas.alec at gmail.com Wed Feb 4 13:58:15 2009 From: leamas.alec at gmail.com (Alec Leamas) Date: Wed, 04 Feb 2009 14:58:15 +0100 Subject: [Ekiga-list] Visual feedback when doing ekiga -c calls In-Reply-To: <498989A7.5010803@gmail.com> References: <498989A7.5010803@gmail.com> Message-ID: <49899EF7.30007@gmail.com> > > Le mercredi 04 f?vrier 2009 ? 13:27 +0100, Alec Leamas a ?crit : > > As of now, if a running ekiga instance makes a call started through > > "ekiga -c #" there is no visual feedback at all. Somehow, when I use > > this, it creates a little uneasy feeling (despite the obvious audio > > feedback). Also, if I lose connection to my account (and thus can't > > receive or place calls), there is still the same green spot in the tray... > > > > Thinking about it, from a user perspective there is really four states: > > > > - "No dialtone" i.e., no registered account. > > - Idle, ready... > > - Connecting > > - Connected > > > > I think it would make sense to reflect all these states in the tray > > icon. Nothing like Skype, which throws up it's main window when a call > > is initiated - it just irritating when you work in another application. > > Maybe just change colour on the green spoot in the tray. Just to > > illustrate what I have in mind: > > > > - No dialtone: Red spot, tooltip "No account registered" > > - Idle: Green spot, tooltip "Diamondcard account registered" or "Two > > accounts registered" > > - Connecting: yellow spot, tooltip "Connecting to "1111111 sip provider com" > > - Connected: as today, tooltip "Connected to "111111 sip provider com" > > > > Or? > > There is maybe a place for that in the main GUI rather than in the > systray (the systray reflect your status already, mixing both status and > connectivity will be overkill). > > I'm thinking about the quality meter at the bottom. It is always visible > and except when you're in a call, it is pretty useless. No dialtone, > idle and connecting can fill this useless, while connected would be > where the quality info will be shown. > > Regards, > Am I missing something? When initiating a call, does the systray icon reflect that we are trying to connect i. e., is there any visual feedback at all when doing a ekiga -c #? As I see it, a call attempt which is not connected is more os less invisible for the user(?). If I lose my account connection, is there any feedback then? Personally, I feel this is more important. I autostart ekiga, which makes sense, if you are logged in you want to be available. But as of now, I really have to check (by opening main window) "now and then" if the line is OK. Is a green light representing a broken phone reasonable? Bottom line: user perspective really is really four states, but the current systray icon only reflects two: Connected or not. To use the main window is better than nothing. But to have to open it just to check if there is a connection is not that good. And, as I said, the "ekiga -c" mechanism is most likely invoked when you work in some other application, and to show the main window then (like Skype) is just little irritating (?) Reading what I've written it feels a little sharp. Hope you don't mind, English is not my native language, the nuances are not lost... I want to be friendly, but writes like God knows what. Have mercy with me :-) --alec From leamas.alec at gmail.com Wed Feb 4 14:08:39 2009 From: leamas.alec at gmail.com (Alec Leamas) Date: Wed, 04 Feb 2009 15:08:39 +0100 Subject: [Ekiga-list] Visual feedback when doing ekiga -c calls In-Reply-To: <1233752359.18030.46.camel@achille> References: <498989A7.5010803@gmail.com> <1233752359.18030.46.camel@achille> Message-ID: <4989A167.90909@gmail.com> yannick wrote: > Le mercredi 04 f?vrier 2009 ? 13:27 +0100, Alec Leamas a ?crit : > >> As of now, if a running ekiga instance makes a call started through >> "ekiga -c #" there is no visual feedback at all. Somehow, when I use >> this, it creates a little uneasy feeling (despite the obvious audio >> feedback). Also, if I lose connection to my account (and thus can't >> receive or place calls), there is still the same green spot in the tray... >> >> Thinking about it, from a user perspective there is really four states: >> >> - "No dialtone" i.e., no registered account. >> - Idle, ready... >> - Connecting >> - Connected >> >> I think it would make sense to reflect all these states in the tray >> icon. Nothing like Skype, which throws up it's main window when a call >> is initiated - it just irritating when you work in another application. >> Maybe just change colour on the green spoot in the tray. Just to >> illustrate what I have in mind: >> >> - No dialtone: Red spot, tooltip "No account registered" >> - Idle: Green spot, tooltip "Diamondcard account registered" or "Two >> accounts registered" >> - Connecting: yellow spot, tooltip "Connecting to "1111111 at sip.provider.com" >> - Connected: as today, tooltip "Connected to "111111 at sip.provider.com" >> >> Or? >> > > There is maybe a place for that in the main GUI rather than in the > systray (the systray reflect your status already, mixing both status and > connectivity will be overkill). > > I'm thinking about the quality meter at the bottom. It is always visible > and except when you're in a call, it is pretty useless. No dialtone, > idle and connecting can fill this useless, while connected would be > where the quality info will be shown. > > Regards, > Yannick > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list Yes, I'm missing something: the "called" state, waiting to pick up the phone. Embarrasing. But not a problem, in this case there is a powerful visual representation :-) From sevmek at free.fr Wed Feb 4 14:37:49 2009 From: sevmek at free.fr (yannick) Date: Wed, 04 Feb 2009 15:37:49 +0100 Subject: [Ekiga-list] Visual feedback when doing ekiga -c calls In-Reply-To: <4989A167.90909@gmail.com> References: <498989A7.5010803@gmail.com> <1233752359.18030.46.camel@achille> <4989A167.90909@gmail.com> Message-ID: <1233758269.18030.51.camel@achille> Le mercredi 04 f?vrier 2009 ? 15:08 +0100, Alec Leamas a ?crit : > Yes, I'm missing something: the "called" state, waiting to pick up > the > phone. Embarrasing. But not a problem, in this case there is a > powerful > visual representation :-) What you missed is this: you can turn the green tray icon to red or orange using the main GUI. This is called presence. Green=on line orange=busy red=do not disturb From leamas.alec at gmail.com Wed Feb 4 15:05:29 2009 From: leamas.alec at gmail.com (Alec Leamas) Date: Wed, 04 Feb 2009 16:05:29 +0100 Subject: [Ekiga-list] Visual feedback when doing ekiga -c calls In-Reply-To: <1233758269.18030.51.camel@achille> References: <498989A7.5010803@gmail.com> <1233752359.18030.46.camel@achille> <4989A167.90909@gmail.com> <1233758269.18030.51.camel@achille> Message-ID: <4989AEB9.6070308@gmail.com> yannick wrote: > Le mercredi 04 f?vrier 2009 ? 15:08 +0100, Alec Leamas a ?crit : > >> Yes, I'm missing something: the "called" state, waiting to pick up >> the >> phone. Embarrasing. But not a problem, in this case there is a >> powerful >> visual representation :-) >> > > What you missed is this: > you can turn the green tray icon to red or orange using the main GUI. > This is called presence. > Green=on line > orange=busy > red=do not disturb > Ah, I'm on Fedora. And after following the presence discussion for Fedora I've put it aside. I get your point. But my point(s) are still valid: there is a need to somehow give some visual feedback when ekiga is making a call initiated by other means than the main window. And there is also a need to communicate the possible fact that we are not available at all when all accounts are down. With this said, the green/red idea was obviously not that great...maybe opening the main window is what's left. Other sip-phones does it, it can't be that bad... From Eugen.Dedu at pu-pm.univ-fcomte.fr Wed Feb 4 15:32:18 2009 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Wed, 04 Feb 2009 16:32:18 +0100 Subject: [Ekiga-list] Ekiga errors using Onesuite and Ekiga account In-Reply-To: <21826246.post@talk.nabble.com> References: <21721344.post@talk.nabble.com> <21826246.post@talk.nabble.com> Message-ID: <4989B502.4070908@pu-pm.univ-fcomte.fr> ZXT wrote: > > > ZXT wrote: >> When I launched the Ekiga application it register without a problem then I >> added http://www.onesuite.com/products_Broadband_Main.asp OneSuite sip >> account . It says "Service Unavailable". >> >> I restart the Ekiga application and now both SIP accounts has an error. >> >> Ekiga.net - Could not register (Illegal status code) >> Onesuite - Could not register (Service unavailable) >> >> Screenshot of Error messages -> >> http://www.nabble.com/file/p21721344/ekiga.JPG ekiga.JPG >> >> Anybody got an idea? >> > > Just bumping my question. Again I'm getting error on both Onesuite and Ekiga > account. Please check screenshot. Could you send -d 4 output? See http://wiki.ekiga.org/index.php/Debugging_Ekiga -- Eugen From dsandras at seconix.com Wed Feb 4 19:08:40 2009 From: dsandras at seconix.com (Damien Sandras) Date: Wed, 04 Feb 2009 20:08:40 +0100 Subject: [Ekiga-list] Ekiga.net VOIP conference server info In-Reply-To: <1233741347.19079.1298445445@webmail.messagingengine.com> References: <1233647706.3413.1298206689@webmail.messagingengine.com> <1233682734.18030.37.camel@achille> <1233686408.5192.1.camel@scorpion.multitel.be> <1233741347.19079.1298445445@webmail.messagingengine.com> Message-ID: <1233774520.4593.4.camel@scorpion.multitel.be> Le mercredi 04 f?vrier 2009 ? 01:55 -0800, john_re a ?crit : > > > > > > Nothing fancy, just regular hw for a server. I'm not sure to truly > > > understand your point here... > > Point: Is there any VOIP specific hardware? Maybe some telecom carrier > grade voice IO capability stuff? Low latency throughput, etc? Maybe > some Digium stuff?? No, nothing. It's a standard server with good bandwidth. > > > > > > In short: > > > The whole software stack is open source. > > > > > Mostly I'm interested in the sw that does the voip conferencing, that > mixes the audio stream. & also control for the conference room - is > there, or can there be made available, easily, some control panel for a > voip conference, that shows status info about the conference members, > the rate & quality of their connections, etc - something to help manage > a conference to any useful extent, & perhaps debug connections, - like > volume levels, etc It could be implemented, but currently it is not available. [...] > > > > > > > 6b) what is the maximum conference participants it can handle > > > > > > I've no clue. I personally tested up to something like 10. We do not know. > > > > 7) What issues should one be aware of in attempting to create a global > > > > conference? Ex: USA & India? > > > > > > It is numeric communication. Thus geographical mesures need to be > > > reconsidered. It mostly depends on the underlying net infrastructure. > > > > > > I do not know Ekiga.net's own limits in this regard. > > > > > Jan? anyone? Same answer here. That question is impossible to answer. -- _ 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 chinku.linux at gmail.com Thu Feb 5 06:31:29 2009 From: chinku.linux at gmail.com (chaitanya mehandru) Date: Thu, 5 Feb 2009 12:01:29 +0530 Subject: [Ekiga-list] E3 on KDE 8.04 will also have h264 enabled soon Message-ID: <24b40b2b0902042231g10bc8287yb9d11d9e23bdbc82@mail.gmail.com> I am working on getting H264 codec support available as well. Will update the group as soon as I am done. I wish to do a VOIP check done with the group on that side before our meeting on Saturday. -------------- next part -------------- An HTML attachment was scrubbed... URL: From john_re at fastmail.us Thu Feb 5 16:18:43 2009 From: john_re at fastmail.us (john_re) Date: Thu, 05 Feb 2009 08:18:43 -0800 Subject: [Ekiga-list] Ekiga.net VOIP conference server info In-Reply-To: <1233774520.4593.4.camel@scorpion.multitel.be> References: <1233647706.3413.1298206689@webmail.messagingengine.com> <1233682734.18030.37.camel@achille> <1233686408.5192.1.camel@scorpion.multitel.be> <1233741347.19079.1298445445@webmail.messagingengine.com> <1233774520.4593.4.camel@scorpion.multitel.be> Message-ID: <1233850723.32479.1298726781@webmail.messagingengine.com> On Wed, 04 Feb 2009 20:08:40 +0100, "Damien Sandras" said: > Le mercredi 04 f?vrier 2009 ? 01:55 -0800, john_re a ?crit : > > > > > > > > Nothing fancy, just regular hw for a server. I'm not sure to truly > > > > understand your point here... > > > > Point: Is there any VOIP specific hardware? Maybe some telecom carrier > > grade voice IO capability stuff? Low latency throughput, etc? Maybe > > some Digium stuff?? > > No, nothing. It's a standard server with good bandwidth. What kind & speed processor? How much RAM? Any ekiga leader want me to add the info in this thread to the ekiga wiki? From leamas.alec at gmail.com Thu Feb 5 23:08:43 2009 From: leamas.alec at gmail.com (Alec Leamas) Date: Fri, 06 Feb 2009 00:08:43 +0100 Subject: [Ekiga-list] Hacking: ekiga-callto In-Reply-To: <1233850723.32479.1298726781@webmail.messagingengine.com> References: <1233647706.3413.1298206689@webmail.messagingengine.com> <1233682734.18030.37.camel@achille> <1233686408.5192.1.camel@scorpion.multitel.be> <1233741347.19079.1298445445@webmail.messagingengine.com> <1233774520.4593.4.camel@scorpion.multitel.be> <1233850723.32479.1298726781@webmail.messagingengine.com> Message-ID: <498B717B.5000603@gmail.com> I've been busy some evenings creating scripts to make ekiga calls from web pages. I am at a point where I can click on any phone number in a web page to make ekiga call this number. Unfortunately, most "real" phone numbers are not given in the standard, international form. So I have faced the need to add missing countrycodes for numbers missing it. This implies a need to configure countrycode etc for the users. There is a simple form for this. If anyone is interested, the scripts are available as rpm and tar.gz packages at ftp://mumin.dnsalias.net/pub/ekiga-callto/ . Also, if anyone think it's worth the effort, some new localisations would be really nice. The README covers how to use the stuff. Cheers, --alec From franz.fuder at ifaz.de Fri Feb 6 10:52:22 2009 From: franz.fuder at ifaz.de (Franz Fuder) Date: Fri, 06 Feb 2009 11:52:22 +0100 Subject: [Ekiga-list] Can not connect to echo server Message-ID: <498C1666.9000006@ifaz.de> Today I compiled the Ekiga out of the svn tree all three components. The build was made on a suse 11.1 and ran without any problems. However when I tried to connect to the echo server it fails. I seems to me that the listner fails for some reasons ? Any thought what I have done wrong, the firewall rules are in place. Regards Franz The ekiga -d 1 shows: 2009/02/06 10:09:53.221 0:03.707 GConf support enabled 2009/02/06 10:09:53.221 0:03.708 ESound support disabled 2009/02/06 10:09:54.924 0:05.410 Opal Liste...0xb49a4b90 Listen UDP read error. 2009/02/06 10:09:54.944 0:05.430 PWLib Destroyed thread 0x83549f0 Opal Listener:0xb49a4b90(id = 0) 2009/02/06 10:09:55.083 0:05.569 PWLib Destroyed thread 0x8366f30 Opal Listener:0xb4963b90(id = 0) From borepstein at gmail.com Fri Feb 6 16:44:32 2009 From: borepstein at gmail.com (Boris Epstein) Date: Fri, 6 Feb 2009 11:44:32 -0500 Subject: [Ekiga-list] Ekiga users to chat with Message-ID: <8fbac5ca0902060844s57e0434rfb9373bd3fd42c1@mail.gmail.com> Hi all, I have just started getting into Ekiga again (last time I tried something didn't click and then I was busy with other things, whatever). So now I am wondering - is there a resource for testing, like a chat room for people available to communicate with others using Ekiga to help them get started. Thanks. Boris. From sevmek at free.fr Fri Feb 6 17:47:35 2009 From: sevmek at free.fr (yannick) Date: Fri, 06 Feb 2009 18:47:35 +0100 Subject: [Ekiga-list] Ekiga users to chat with In-Reply-To: <8fbac5ca0902060844s57e0434rfb9373bd3fd42c1@mail.gmail.com> References: <8fbac5ca0902060844s57e0434rfb9373bd3fd42c1@mail.gmail.com> Message-ID: <1233942455.8223.17.camel@achille> Le vendredi 06 f?vrier 2009 ? 11:44 -0500, Boris Epstein a ?crit : > Hi all, > > I have just started getting into Ekiga again (last time I tried > something didn't click and then I was busy with other things, > whatever). So now I am wondering - is there a resource for testing, > like a chat room for people available to communicate with others using > Ekiga to help them get started. > https://www.ekiga.net/index.php?page=services http://wiki.ekiga.org/index.php/Fun_Numbers > Thanks. > > Boris. > _______________________________________________ > 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 borepstein at gmail.com Fri Feb 6 18:06:35 2009 From: borepstein at gmail.com (Boris Epstein) Date: Fri, 6 Feb 2009 13:06:35 -0500 Subject: [Ekiga-list] Ekiga users to chat with In-Reply-To: <1233942455.8223.17.camel@achille> References: <8fbac5ca0902060844s57e0434rfb9373bd3fd42c1@mail.gmail.com> <1233942455.8223.17.camel@achille> Message-ID: <8fbac5ca0902061006j2b0fccc5id67c001a3e7d97e4@mail.gmail.com> On Fri, Feb 6, 2009 at 12:47 PM, yannick wrote: > > > > https://www.ekiga.net/index.php?page=services > > http://wiki.ekiga.org/index.php/Fun_Numbers > > > Thanks. I tried the call back test number and no one called me back thus far. Not that I am seeking attention - but could those of you who are online and don't mind try calling me back? The address is: borepstein at ekiga.net Thanks. Boris. -------------- next part -------------- An HTML attachment was scrubbed... URL: From borepstein at gmail.com Fri Feb 6 18:22:23 2009 From: borepstein at gmail.com (Boris Epstein) Date: Fri, 6 Feb 2009 13:22:23 -0500 Subject: [Ekiga-list] Ekiga users to chat with In-Reply-To: <498C7EE7.6080904@pu-pm.univ-fcomte.fr> References: <8fbac5ca0902060844s57e0434rfb9373bd3fd42c1@mail.gmail.com> <1233942455.8223.17.camel@achille> <8fbac5ca0902061006j2b0fccc5id67c001a3e7d97e4@mail.gmail.com> <498C7D10.5000802@pu-pm.univ-fcomte.fr> <8fbac5ca0902061013s6e269ce0v2bf50ed453a179cb@mail.gmail.com> <498C7EE7.6080904@pu-pm.univ-fcomte.fr> Message-ID: <8fbac5ca0902061022y7b42622qcd12fd74795f993a@mail.gmail.com> On Fri, Feb 6, 2009 at 1:18 PM, Eugen Dedu wrote: > Boris Epstein wrote: > >> On Fri, Feb 6, 2009 at 1:10 PM, Eugen Dedu >> wrote: >> >> Boris Epstein wrote: >>> >>> On Fri, Feb 6, 2009 at 12:47 PM, yannick wrote: >>>> >>> > Have you seen my message through ekiga? I receive "User not available" > when I call you... > > -- > Eugen Yes, I have. However, I was not able to respond to you. So indeed the problem appears to be on this end. Thanks, a lot, Eugen! I have to go offline right now, but at least now I know what to look into. Cheers, Boris. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Eugen.Dedu at pu-pm.univ-fcomte.fr Fri Feb 6 18:26:53 2009 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Fri, 06 Feb 2009 19:26:53 +0100 Subject: [Ekiga-list] Ekiga debian snapshots Message-ID: <498C80ED.9020306@pu-pm.univ-fcomte.fr> Hi, Starting from tomorrow, ekiga debian snapshots (http://wiki.ekiga.org/index.php/Snapshots) can be installed along with ekiga package, which means that gnome-desktop-environment needs not to be uninstalled. For the moment, snapshots are compiled without dbus support (building errors still to be fixed) and without the new gstreamer support (dependencies found on debian/experimental for the moment). However I hope to activate them soon. Also, note that the gconf settings name is not ekiga anymore, but ekiga-snapshot. This means it does not interfere with ekiga, and that the gconf settings for ekiga-snapshot can be empty for you the first time... The executable also is called now ekiga-snapshot. Cheers, -- Eugen Dedu From bbagger at gmail.com Fri Feb 6 19:15:03 2009 From: bbagger at gmail.com (Bent) Date: Fri, 6 Feb 2009 20:15:03 +0100 Subject: [Ekiga-list] Ekiga users to chat with In-Reply-To: <8fbac5ca0902061022y7b42622qcd12fd74795f993a@mail.gmail.com> References: <8fbac5ca0902060844s57e0434rfb9373bd3fd42c1@mail.gmail.com> <1233942455.8223.17.camel@achille> <8fbac5ca0902061006j2b0fccc5id67c001a3e7d97e4@mail.gmail.com> <498C7D10.5000802@pu-pm.univ-fcomte.fr> <8fbac5ca0902061013s6e269ce0v2bf50ed453a179cb@mail.gmail.com> <498C7EE7.6080904@pu-pm.univ-fcomte.fr> <8fbac5ca0902061022y7b42622qcd12fd74795f993a@mail.gmail.com> Message-ID: <2e19719f0902061115y648be423rbddd4c15df4a3ee7@mail.gmail.com> Hi I have created a 'call-me' service on my Asterisk. If you call sip:124 at ast4.oz6bl.dk you should get hung up and then get a call back from my time service within a few seconds. The service is experimental and not tested very thoroughly, so I would appreciate any comments on it. In any case: have fun. Kind regards, Bent From dsandras at seconix.com Sat Feb 7 09:28:06 2009 From: dsandras at seconix.com (Damien Sandras) Date: Sat, 07 Feb 2009 10:28:06 +0100 Subject: [Ekiga-list] Ekiga.net VOIP conference server info In-Reply-To: <1233850723.32479.1298726781@webmail.messagingengine.com> References: <1233647706.3413.1298206689@webmail.messagingengine.com> <1233682734.18030.37.camel@achille> <1233686408.5192.1.camel@scorpion.multitel.be> <1233741347.19079.1298445445@webmail.messagingengine.com> <1233774520.4593.4.camel@scorpion.multitel.be> <1233850723.32479.1298726781@webmail.messagingengine.com> Message-ID: <1233998886.4242.1.camel@scorpion.multitel.be> Le jeudi 05 f?vrier 2009 ? 08:18 -0800, john_re a ?crit : > On Wed, 04 Feb 2009 20:08:40 +0100, "Damien Sandras" > said: > > Le mercredi 04 f?vrier 2009 ? 01:55 -0800, john_re a ?crit : > > > > > > > > > > Nothing fancy, just regular hw for a server. I'm not sure to truly > > > > > understand your point here... > > > > > > Point: Is there any VOIP specific hardware? Maybe some telecom carrier > > > grade voice IO capability stuff? Low latency throughput, etc? Maybe > > > some Digium stuff?? > > > > No, nothing. It's a standard server with good bandwidth. > > What kind & speed processor? How much RAM? > AMD Opteron 2800 MHz, apparently only 1GB of RAM. > Any ekiga leader want me to add the info in this thread to the ekiga > wiki? Yannick ? -- _ 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 Feb 7 09:29:19 2009 From: dsandras at seconix.com (Damien Sandras) Date: Sat, 07 Feb 2009 10:29:19 +0100 Subject: [Ekiga-list] Hacking: ekiga-callto In-Reply-To: <498B717B.5000603@gmail.com> References: <1233647706.3413.1298206689@webmail.messagingengine.com> <1233682734.18030.37.camel@achille> <1233686408.5192.1.camel@scorpion.multitel.be> <1233741347.19079.1298445445@webmail.messagingengine.com> <1233774520.4593.4.camel@scorpion.multitel.be> <1233850723.32479.1298726781@webmail.messagingengine.com> <498B717B.5000603@gmail.com> Message-ID: <1233998959.4242.3.camel@scorpion.multitel.be> Le vendredi 06 f?vrier 2009 ? 00:08 +0100, Alec Leamas a ?crit : > I've been busy some evenings creating scripts to make ekiga calls from > web pages. I am at a point where I can click on any phone number in a > web page to make ekiga call this number. > > Unfortunately, most "real" phone numbers are not given in the standard, > international form. So I have faced the need to add missing countrycodes > for numbers missing it. This implies a need to configure countrycode etc > for the users. There is a simple form for this. > > If anyone is interested, the scripts are available as rpm and tar.gz > packages at > ftp://mumin.dnsalias.net/pub/ekiga-callto/ . Also, if anyone think it's > worth the effort, > some new localisations would be really nice. The README covers how to > use the > stuff. Thanks for this work! Yannick, could we link to this from the wiki together with the Ekiga.net web buttons? -- _ 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 Feb 7 09:31:42 2009 From: dsandras at seconix.com (Damien Sandras) Date: Sat, 07 Feb 2009 10:31:42 +0100 Subject: [Ekiga-list] Can not connect to echo server In-Reply-To: <498C1666.9000006@ifaz.de> References: <498C1666.9000006@ifaz.de> Message-ID: <1233999102.4242.6.camel@scorpion.multitel.be> Le vendredi 06 f?vrier 2009 ? 11:52 +0100, Franz Fuder a ?crit : > Today I compiled the Ekiga out of the svn tree all three components. The > build was made on a suse 11.1 and ran without any problems. > > However when I tried to connect to the echo server it fails. I seems to > me that the listner fails for some reasons ? > > Any thought what I have done wrong, the firewall rules are in place. For some reason (that I ignore), it can not bind to the 5060 port. It could happen if you do not have any network interface 'up', or if something prevents it to bind to that port (some kernel security patch for example). -- _ 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 Feb 7 09:32:15 2009 From: dsandras at seconix.com (Damien Sandras) Date: Sat, 07 Feb 2009 10:32:15 +0100 Subject: [Ekiga-list] Ekiga debian snapshots In-Reply-To: <498C80ED.9020306@pu-pm.univ-fcomte.fr> References: <498C80ED.9020306@pu-pm.univ-fcomte.fr> Message-ID: <1233999135.4242.8.camel@scorpion.multitel.be> Le vendredi 06 f?vrier 2009 ? 19:26 +0100, Eugen Dedu a ?crit : > Hi, > > Starting from tomorrow, ekiga debian snapshots > (http://wiki.ekiga.org/index.php/Snapshots) can be installed along with > ekiga package, which means that gnome-desktop-environment needs not to > be uninstalled. > > For the moment, snapshots are compiled without dbus support (building > errors still to be fixed) and without the new gstreamer support > (dependencies found on debian/experimental for the moment). However I > hope to activate them soon. > > Also, note that the gconf settings name is not ekiga anymore, but > ekiga-snapshot. This means it does not interfere with ekiga, and that > the gconf settings for ekiga-snapshot can be empty for you the first > time... The executable also is called now ekiga-snapshot. 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 sevmek at free.fr Sat Feb 7 11:12:52 2009 From: sevmek at free.fr (yannick) Date: Sat, 07 Feb 2009 12:12:52 +0100 Subject: [Ekiga-list] Ekiga.net VOIP conference server info In-Reply-To: <1233998886.4242.1.camel@scorpion.multitel.be> References: <1233647706.3413.1298206689@webmail.messagingengine.com> <1233682734.18030.37.camel@achille> <1233686408.5192.1.camel@scorpion.multitel.be> <1233741347.19079.1298445445@webmail.messagingengine.com> <1233774520.4593.4.camel@scorpion.multitel.be> <1233850723.32479.1298726781@webmail.messagingengine.com> <1233998886.4242.1.camel@scorpion.multitel.be> Message-ID: <1234005172.8223.32.camel@achille> Le samedi 07 f?vrier 2009 ? 10:28 +0100, Damien Sandras a ?crit : > > Any ekiga leader want me to add the info in this thread to the ekiga > > wiki? > > Yannick ? It is here for now: http://wiki.ekiga.org/index.php/Ekiga.net_VoIP_service_subscription#FAQ From sevmek at free.fr Sat Feb 7 11:14:02 2009 From: sevmek at free.fr (yannick) Date: Sat, 07 Feb 2009 12:14:02 +0100 Subject: [Ekiga-list] Ekiga.net VOIP conference server info In-Reply-To: <1233850723.32479.1298726781@webmail.messagingengine.com> References: <1233647706.3413.1298206689@webmail.messagingengine.com> <1233682734.18030.37.camel@achille> <1233686408.5192.1.camel@scorpion.multitel.be> <1233741347.19079.1298445445@webmail.messagingengine.com> <1233774520.4593.4.camel@scorpion.multitel.be> <1233850723.32479.1298726781@webmail.messagingengine.com> Message-ID: <1234005242.8223.34.camel@achille> Le jeudi 05 f?vrier 2009 ? 08:18 -0800, john_re a ?crit : > Any ekiga leader want me to add the info in this thread to the ekiga > wiki? Do you want writable access to the wiki? From franz.fuder at ifaz.de Sat Feb 7 13:00:13 2009 From: franz.fuder at ifaz.de (Franz Fuder) Date: Sat, 07 Feb 2009 14:00:13 +0100 Subject: [Ekiga-list] Can not connect to echo server In-Reply-To: <1233999102.4242.6.camel@scorpion.multitel.be> References: <498C1666.9000006@ifaz.de> <1233999102.4242.6.camel@scorpion.multitel.be> Message-ID: <498D85DD.6090003@ifaz.de> Damien Sandras schrieb: > Le vendredi 06 f?vrier 2009 ? 11:52 +0100, Franz Fuder a ?crit : > >> Today I compiled the Ekiga out of the svn tree all three components. The >> build was made on a suse 11.1 and ran without any problems. >> >> However when I tried to connect to the echo server it fails. I seems to >> me that the listner fails for some reasons ? >> >> Any thought what I have done wrong, the firewall rules are in place. >> > > For some reason (that I ignore), it can not bind to the 5060 port. It > could happen if you do not have any network interface 'up', or if > something prevents it to bind to that port (some kernel security patch > for example). > Ops pressed the send button too early, here the final mail. I checked the port 5060 and the network, there is only one eth0 up and running. I installed the ekiga from suse: ---------- 2009/02/07 11:58:47.510 0:00.131 ekiga Version 3.0.1 by on Unix Linux (2.6.27.7-9-pae-i686) at 2009/2/7 11:58:47.510 2009/02/07 11:58:47.510 0:00.131 ekiga Ekiga SVN revision: unknown ----------- and it runs fine, I can connect to the echo server. I guess from the network everything should be fine in case not the suse ekiga versions should also not connect to the echo server. When I run the last svn version with ekiga -d 3 I get: --------- 2009/02/07 13:49:38.447 0:07.164 Opal Liste...0xb489bb90 OpalUDP Binding to interface: 88.152.92.142:5060 2009/02/07 13:49:38.448 0:07.165 Opal Liste...0xb489bb90 SIP PDU 202 OK received: rem=udp$86.64.162.35:5060,local=udp$88.152.92.142:5060,if=192.168.1.3%eth0 --------- seems to me that the binding is ok of the port. I get some messages with PDU too large ? Is the PDU the problem ? after I get: -------- 009/02/07 13:49:55.432 0:24.149 Housekeeper:0xb48dcb90 SIP Transaction 1 INVITE timeout, making retry 1 2009/02/07 13:49:55.436 0:24.153 Housekeeper:0xb48dcb90 OpalPlugin to_customised_options changed option "MaxBR" from "0" to "40960" 2009/02/07 13:49:55.449 0:24.166 Housekeeper:0xb48dcb90 OpalPlugin to_customised_options changed option "MaxBR" from "0" to "40960" 2009/02/07 13:49:55.454 0:24.171 Housekeeper:0xb48dcb90 SIP PDU is likely too large (1703 bytes) for UDP datagram. 2009/02/07 13:49:55.454 0:24.171 Housekeeper:0xb48dcb90 SIP Sending PDU INVITE sip:500 at ekiga.net (1703 bytes) to: rem=udp$86.64.162.35:5060,local=udp$88.152.92.142:5060,if=192.168.1.3%eth0 2009/02/07 13:49:55.455 0:24.172 Housekeeper:0xb48dcb90 OpalUDP Setting interface to 192.168.1.3%eth0 2009/02/07 13:49:56.455 0:25.172 Housekeeper:0xb48dcb90 SIP Transaction 1 INVITE timeout, making retry 2 2009/02/07 13:49:56.459 0:25.176 Housekeeper:0xb48dcb90 OpalPlugin to_customised_options changed option "MaxBR" from "0" to "40960" 2009/02/07 13:49:56.469 0:25.186 Housekeeper:0xb48dcb90 OpalPlugin to_customised_options changed option "MaxBR" from "0" to "40960" 2009/02/07 13:49:56.475 0:25.192 Housekeeper:0xb48dcb90 SIP PDU is likely too large (1703 bytes) for UDP datagram. 2009/02/07 13:49:56.475 0:25.192 Housekeeper:0xb48dcb90 SIP Sending PDU INVITE sip:500 at ekiga.net (1703 bytes) to: rem=udp$86.64.162.35:5060,local=udp$88.152.92.142:5060,if=192.168.1.3%eth0 2009/02/07 13:49:56.476 0:25.193 Housekeeper:0xb48dcb90 OpalUDP Setting interface to 192.168.1.3%eth0 2009/02/07 13:49:58.477 0:27.194 Housekeeper:0xb48dcb90 SIP Transaction 1 INVITE timeout, making retry 3 2009/02/07 13:49:58.480 0:27.197 Housekeeper:0xb48dcb90 OpalPlugin to_customised_options changed option "MaxBR" from "0" to "40960" 2009/02/07 13:49:58.489 0:27.206 Housekeeper:0xb48dcb90 OpalPlugin to_customised_options changed option "MaxBR" from "0" to "40960" 2009/02/07 13:49:58.497 0:27.214 Housekeeper:0xb48dcb90 SIP PDU is likely too large (1703 bytes) for UDP datagram. --------- regards Franz -------------- next part -------------- An HTML attachment was scrubbed... URL: From dsandras at seconix.com Sat Feb 7 13:06:34 2009 From: dsandras at seconix.com (Damien Sandras) Date: Sat, 07 Feb 2009 14:06:34 +0100 Subject: [Ekiga-list] Can not connect to echo server In-Reply-To: <498D85DD.6090003@ifaz.de> References: <498C1666.9000006@ifaz.de> <1233999102.4242.6.camel@scorpion.multitel.be> <498D85DD.6090003@ifaz.de> Message-ID: <1234011994.4242.12.camel@scorpion.multitel.be> Le samedi 07 f?vrier 2009 ? 14:00 +0100, Franz Fuder a ?crit : > Damien Sandras schrieb: > > Le vendredi 06 f?vrier 2009 ? 11:52 +0100, Franz Fuder a ?crit : > > > > > Today I compiled the Ekiga out of the svn tree all three components. The > > > build was made on a suse 11.1 and ran without any problems. > > > > > > However when I tried to connect to the echo server it fails. I seems to > > > me that the listner fails for some reasons ? > > > > > > Any thought what I have done wrong, the firewall rules are in place. > > > > > > > For some reason (that I ignore), it can not bind to the 5060 port. It > > could happen if you do not have any network interface 'up', or if > > something prevents it to bind to that port (some kernel security patch > > for example). > > > Ops pressed the send button too early, here the final mail. > > > I checked the port 5060 and the network, there is only one eth0 up and > running. I installed the ekiga from suse: > ---------- > 2009/02/07 11:58:47.510 0:00.131 ekiga > Version 3.0.1 by on Unix Linux (2.6.27.7-9-pae-i686) at 2009/2/7 > 11:58:47.510 > 2009/02/07 11:58:47.510 0:00.131 ekiga Ekiga > SVN revision: unknown > ----------- > and it runs fine, I can connect to the echo server. I guess from the > network everything should be fine in case not the suse ekiga versions > should also not connect to the echo server. > > When I run the last svn version with ekiga -d 3 I get: > --------- > 2009/02/07 13:49:38.447 0:07.164 Opal Liste...0xb489bb90 > OpalUDP Binding to interface: > 88.152.92.142:5060 > 2009/02/07 13:49:38.448 0:07.165 Opal Liste...0xb489bb90 SIP > PDU 202 OK received: rem=udp$86.64.162.35:5060,local=udp > $88.152.92.142:5060,if=192.168.1.3% > eth0 > --------- > > seems to me that the binding is ok of the port. I get some messages > with PDU too large ? Is the PDU the problem ? > after I get: > > -------- > 009/02/07 13:49:55.432 0:24.149 Housekeeper:0xb48dcb90 SIP > Transaction 1 INVITE timeout, making retry > 1 > 2009/02/07 13:49:55.436 0:24.153 Housekeeper:0xb48dcb90 > OpalPlugin to_customised_options changed option "MaxBR" from "0" > to > "40960" > 2009/02/07 13:49:55.449 0:24.166 Housekeeper:0xb48dcb90 > OpalPlugin to_customised_options changed option "MaxBR" from "0" > to > "40960" > 2009/02/07 13:49:55.454 0:24.171 Housekeeper:0xb48dcb90 SIP > PDU is likely too large (1703 bytes) for UDP > datagram. > 2009/02/07 13:49:55.454 0:24.171 Housekeeper:0xb48dcb90 SIP > Sending PDU INVITE sip:500 at ekiga.net (1703 bytes) to: rem=udp > $86.64.162.35:5060,local=udp$88.152.92.142:5060,if=192.168.1.3% > eth0 > 2009/02/07 13:49:55.455 0:24.172 Housekeeper:0xb48dcb90 > OpalUDP Setting interface to 192.168.1.3% > eth0 > 2009/02/07 13:49:56.455 0:25.172 Housekeeper:0xb48dcb90 SIP > Transaction 1 INVITE timeout, making retry > 2 > 2009/02/07 13:49:56.459 0:25.176 Housekeeper:0xb48dcb90 > OpalPlugin to_customised_options changed option "MaxBR" from "0" > to > "40960" > 2009/02/07 13:49:56.469 0:25.186 Housekeeper:0xb48dcb90 > OpalPlugin to_customised_options changed option "MaxBR" from "0" > to > "40960" > 2009/02/07 13:49:56.475 0:25.192 Housekeeper:0xb48dcb90 SIP > PDU is likely too large (1703 bytes) for UDP > datagram. > 2009/02/07 13:49:56.475 0:25.192 Housekeeper:0xb48dcb90 SIP > Sending PDU INVITE sip:500 at ekiga.net (1703 bytes) to: rem=udp > $86.64.162.35:5060,local=udp$88.152.92.142:5060,if=192.168.1.3% > eth0 > 2009/02/07 13:49:56.476 0:25.193 Housekeeper:0xb48dcb90 > OpalUDP Setting interface to 192.168.1.3% > eth0 > 2009/02/07 13:49:58.477 0:27.194 Housekeeper:0xb48dcb90 SIP > Transaction 1 INVITE timeout, making retry > 3 > 2009/02/07 13:49:58.480 0:27.197 Housekeeper:0xb48dcb90 > OpalPlugin to_customised_options changed option "MaxBR" from "0" > to > "40960" > 2009/02/07 13:49:58.489 0:27.206 Housekeeper:0xb48dcb90 > OpalPlugin to_customised_options changed option "MaxBR" from "0" > to > "40960" > 2009/02/07 13:49:58.497 0:27.214 Housekeeper:0xb48dcb90 SIP > PDU is likely too large (1703 bytes) for UDP > datagram. Perhaps you enabled all codecs with all options ? -- _ 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 franz.fuder at ifaz.de Sat Feb 7 13:18:40 2009 From: franz.fuder at ifaz.de (Franz Fuder) Date: Sat, 07 Feb 2009 14:18:40 +0100 Subject: [Ekiga-list] Can not connect to echo server In-Reply-To: <1234011994.4242.12.camel@scorpion.multitel.be> References: <498C1666.9000006@ifaz.de> <1233999102.4242.6.camel@scorpion.multitel.be> <498D85DD.6090003@ifaz.de> <1234011994.4242.12.camel@scorpion.multitel.be> Message-ID: <498D8A30.1050608@ifaz.de> Damien Sandras schrieb: > Le samedi 07 f?vrier 2009 ? 14:00 +0100, Franz Fuder a ?crit : > >> Damien Sandras schrieb: >> >>> Le vendredi 06 f?vrier 2009 ? 11:52 +0100, Franz Fuder a ?crit : >>> >>> >>>> Today I compiled the Ekiga out of the svn tree all three components. The >>>> build was made on a suse 11.1 and ran without any problems. >>>> >>>> However when I tried to connect to the echo server it fails. I seems to >>>> me that the listner fails for some reasons ? >>>> >>>> Any thought what I have done wrong, the firewall rules are in place. >>>> >>>> >>> For some reason (that I ignore), it can not bind to the 5060 port. It >>> could happen if you do not have any network interface 'up', or if >>> something prevents it to bind to that port (some kernel security patch >>> for example). >>> >>> >> Ops pressed the send button too early, here the final mail. >> >> >> I checked the port 5060 and the network, there is only one eth0 up and >> running. I installed the ekiga from suse: >> ---------- >> 2009/02/07 11:58:47.510 0:00.131 ekiga >> Version 3.0.1 by on Unix Linux (2.6.27.7-9-pae-i686) at 2009/2/7 >> 11:58:47.510 >> 2009/02/07 11:58:47.510 0:00.131 ekiga Ekiga >> SVN revision: unknown >> ----------- >> and it runs fine, I can connect to the echo server. I guess from the >> network everything should be fine in case not the suse ekiga versions >> should also not connect to the echo server. >> >> When I run the last svn version with ekiga -d 3 I get: >> --------- >> 2009/02/07 13:49:38.447 0:07.164 Opal Liste...0xb489bb90 >> OpalUDP Binding to interface: >> 88.152.92.142:5060 >> 2009/02/07 13:49:38.448 0:07.165 Opal Liste...0xb489bb90 SIP >> PDU 202 OK received: rem=udp$86.64.162.35:5060,local=udp >> $88.152.92.142:5060,if=192.168.1.3% >> eth0 >> --------- >> >> seems to me that the binding is ok of the port. I get some messages >> with PDU too large ? Is the PDU the problem ? >> after I get: >> >> -------- >> 009/02/07 13:49:55.432 0:24.149 Housekeeper:0xb48dcb90 SIP >> Transaction 1 INVITE timeout, making retry >> 1 >> 2009/02/07 13:49:55.436 0:24.153 Housekeeper:0xb48dcb90 >> OpalPlugin to_customised_options changed option "MaxBR" from "0" >> to >> "40960" >> 2009/02/07 13:49:55.449 0:24.166 Housekeeper:0xb48dcb90 >> OpalPlugin to_customised_options changed option "MaxBR" from "0" >> to >> "40960" >> 2009/02/07 13:49:55.454 0:24.171 Housekeeper:0xb48dcb90 SIP >> PDU is likely too large (1703 bytes) for UDP >> datagram. >> 2009/02/07 13:49:55.454 0:24.171 Housekeeper:0xb48dcb90 SIP >> Sending PDU INVITE sip:500 at ekiga.net (1703 bytes) to: rem=udp >> $86.64.162.35:5060,local=udp$88.152.92.142:5060,if=192.168.1.3% >> eth0 >> 2009/02/07 13:49:55.455 0:24.172 Housekeeper:0xb48dcb90 >> OpalUDP Setting interface to 192.168.1.3% >> eth0 >> 2009/02/07 13:49:56.455 0:25.172 Housekeeper:0xb48dcb90 SIP >> Transaction 1 INVITE timeout, making retry >> 2 >> 2009/02/07 13:49:56.459 0:25.176 Housekeeper:0xb48dcb90 >> OpalPlugin to_customised_options changed option "MaxBR" from "0" >> to >> "40960" >> 2009/02/07 13:49:56.469 0:25.186 Housekeeper:0xb48dcb90 >> OpalPlugin to_customised_options changed option "MaxBR" from "0" >> to >> "40960" >> 2009/02/07 13:49:56.475 0:25.192 Housekeeper:0xb48dcb90 SIP >> PDU is likely too large (1703 bytes) for UDP >> datagram. >> 2009/02/07 13:49:56.475 0:25.192 Housekeeper:0xb48dcb90 SIP >> Sending PDU INVITE sip:500 at ekiga.net (1703 bytes) to: rem=udp >> $86.64.162.35:5060,local=udp$88.152.92.142:5060,if=192.168.1.3% >> eth0 >> 2009/02/07 13:49:56.476 0:25.193 Housekeeper:0xb48dcb90 >> OpalUDP Setting interface to 192.168.1.3% >> eth0 >> 2009/02/07 13:49:58.477 0:27.194 Housekeeper:0xb48dcb90 SIP >> Transaction 1 INVITE timeout, making retry >> 3 >> 2009/02/07 13:49:58.480 0:27.197 Housekeeper:0xb48dcb90 >> OpalPlugin to_customised_options changed option "MaxBR" from "0" >> to >> "40960" >> 2009/02/07 13:49:58.489 0:27.206 Housekeeper:0xb48dcb90 >> OpalPlugin to_customised_options changed option "MaxBR" from "0" >> to >> "40960" >> 2009/02/07 13:49:58.497 0:27.214 Housekeeper:0xb48dcb90 SIP >> PDU is likely too large (1703 bytes) for UDP >> datagram. >> > > Perhaps you enabled all codecs with all options ? > Yes I have done, is this not correct ? Which one could I use ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From dsandras at seconix.com Sat Feb 7 14:00:39 2009 From: dsandras at seconix.com (Damien Sandras) Date: Sat, 07 Feb 2009 15:00:39 +0100 Subject: [Ekiga-list] Can not connect to echo server In-Reply-To: <498D8A30.1050608@ifaz.de> References: <498C1666.9000006@ifaz.de> <1233999102.4242.6.camel@scorpion.multitel.be> <498D85DD.6090003@ifaz.de> <1234011994.4242.12.camel@scorpion.multitel.be> <498D8A30.1050608@ifaz.de> Message-ID: <1234015239.4242.14.camel@scorpion.multitel.be> Le samedi 07 f?vrier 2009 ? 14:18 +0100, Franz Fuder a ?crit : > > > > Perhaps you enabled all codecs with all options ? > > > Yes I have done, is this not correct ? Which one could I use ? Just those you need... -- _ 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 franz.fuder at ifaz.de Sat Feb 7 14:06:51 2009 From: franz.fuder at ifaz.de (Franz Fuder) Date: Sat, 07 Feb 2009 15:06:51 +0100 Subject: [Ekiga-list] Can not connect to echo server In-Reply-To: <1234015239.4242.14.camel@scorpion.multitel.be> References: <498C1666.9000006@ifaz.de> <1233999102.4242.6.camel@scorpion.multitel.be> <498D85DD.6090003@ifaz.de> <1234011994.4242.12.camel@scorpion.multitel.be> <498D8A30.1050608@ifaz.de> <1234015239.4242.14.camel@scorpion.multitel.be> Message-ID: <498D957B.3070708@ifaz.de> Damien Sandras schrieb: > Le samedi 07 f?vrier 2009 ? 14:18 +0100, Franz Fuder a ?crit : > >>> Perhaps you enabled all codecs with all options ? >>> >>> >> Yes I have done, is this not correct ? Which one could I use ? >> > > Just those you need... > Thanks for the tip, in the audio section all the codecs are fine. In the video section only the h261 the first one is working. If I activate one of the others it can not connect only with the h261 it can connect wiht the server. I used the echo cancellation but when I use the USB Cam mic I get terrible echoes. Franz -------------- next part -------------- An HTML attachment was scrubbed... URL: From jbwells at blueyonder.co.uk Sat Feb 7 14:19:25 2009 From: jbwells at blueyonder.co.uk (Joe Wells) Date: Sat, 07 Feb 2009 14:19:25 +0000 Subject: [Ekiga-list] Ekiga users to chat with In-Reply-To: <2e19719f0902061115y648be423rbddd4c15df4a3ee7@mail.gmail.com> (Bent's message of "Fri\, 6 Feb 2009 20\:15\:03 +0100") References: <8fbac5ca0902060844s57e0434rfb9373bd3fd42c1@mail.gmail.com> <1233942455.8223.17.camel@achille> <8fbac5ca0902061006j2b0fccc5id67c001a3e7d97e4@mail.gmail.com> <498C7D10.5000802@pu-pm.univ-fcomte.fr> <8fbac5ca0902061013s6e269ce0v2bf50ed453a179cb@mail.gmail.com> <498C7EE7.6080904@pu-pm.univ-fcomte.fr> <8fbac5ca0902061022y7b42622qcd12fd74795f993a@mail.gmail.com> <2e19719f0902061115y648be423rbddd4c15df4a3ee7@mail.gmail.com> Message-ID: <8663jme3de.fsf@blueyonder.co.uk> Bent writes: > I have created a 'call-me' service on my Asterisk. If you call > sip:124 at ast4.oz6bl.dk you should get hung up and then get a call back > from my time service within a few seconds. > > The service is experimental and not tested very thoroughly, so I would > appreciate any comments on it. > > In any case: have fun. Yes, excellent! I was really looking for something like this earlier! Perhaps this could become one of the ?official? ekiga.net services? -- With my best regards, Joe From leamas.alec at gmail.com Sat Feb 7 15:36:42 2009 From: leamas.alec at gmail.com (Alec Leamas) Date: Sat, 07 Feb 2009 16:36:42 +0100 Subject: [Ekiga-list] Revisited: visual feedback when making dbus/cli calls Message-ID: <498DAA8A.9080307@gmail.com> I'm currently using the Dbus interface to establish Ekiga calls. The basic functionality seems fine, but to my understanding there are some glitches: - When making an ekiga.Call(uri)/ekiga.Show() sequence, the call is indeed placed to the uri. Also, if there is no open window, a main window is opened. In this the hook is off (red phone), but the uri called is not reflected in the "dialpad" entry up-left. Net result from a visual, user perspective is some kind of "invisible" call (besides the history, where it eventually is listed). - If the window is open already, it's likely to be hidden by other windows. In this situation the Show() method seems to do nothing. I think it would be more intuitive if the window popped up after a Show() call instead of staying hidden in this situation. From admin at singulartechnologysolutions.com Sat Feb 7 16:25:24 2009 From: admin at singulartechnologysolutions.com (admin at singulartechnologysolutions.com) Date: Sat, 7 Feb 2009 10:25:24 -0600 Subject: [Ekiga-list] Ekiga & Logitech QuickCam Pro 9000 References: <498DAA8A.9080307@gmail.com> Message-ID: <235DE996D4894C2FB38409884031FD86@mjc> Has anyone had success using Ekiga with a Logitech QuickCam Pro 9000 (win32 version)? I tried it a few months ago, and on the echo test it produced pretty nasty loopback/echo/background noise suppression effects, as if the options in Ekiga had no effect. I decided to wait a couple of months and try again to see if new development resolved the issue, but had the same results. This Logitech is not at all an off brand or marginal product - in fact I paid a bit more to get it because of the good reviews I had read. It works fine in other apps and setup/calibration tests sound great. Any idea what might be the problem, or when Ekiga might have a chance of supporting it? -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: multipart/alternative Size: 1 bytes Desc: not available URL: -------------- next part -------------- No virus found in this outgoing message. Checked by AVG - www.avg.com Version: 8.0.233 / Virus Database: 270.10.19/1938 - Release Date: 02/06/09 11:31:00 From dsandras at seconix.com Sat Feb 7 16:37:03 2009 From: dsandras at seconix.com (Damien Sandras) Date: Sat, 07 Feb 2009 17:37:03 +0100 Subject: [Ekiga-list] Ekiga users to chat with In-Reply-To: <8663jme3de.fsf@blueyonder.co.uk> References: <8fbac5ca0902060844s57e0434rfb9373bd3fd42c1@mail.gmail.com> <1233942455.8223.17.camel@achille> <8fbac5ca0902061006j2b0fccc5id67c001a3e7d97e4@mail.gmail.com> <498C7D10.5000802@pu-pm.univ-fcomte.fr> <8fbac5ca0902061013s6e269ce0v2bf50ed453a179cb@mail.gmail.com> <498C7EE7.6080904@pu-pm.univ-fcomte.fr> <8fbac5ca0902061022y7b42622qcd12fd74795f993a@mail.gmail.com> <2e19719f0902061115y648be423rbddd4c15df4a3ee7@mail.gmail.com> <8663jme3de.fsf@blueyonder.co.uk> Message-ID: <1234024623.4242.16.camel@scorpion.multitel.be> Le samedi 07 f?vrier 2009 ? 14:19 +0000, Joe Wells a ?crit : > Bent writes: > > > I have created a 'call-me' service on my Asterisk. If you call > > sip:124 at ast4.oz6bl.dk you should get hung up and then get a call back > > from my time service within a few seconds. > > > > The service is experimental and not tested very thoroughly, so I would > > appreciate any comments on it. > > > > In any case: have fun. > > Yes, excellent! I was really looking for something like this earlier! > > Perhaps this could become one of the ?official? ekiga.net services? > I think 520 at ekiga.net does the same. -- _ 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 Feb 7 16:37:43 2009 From: dsandras at seconix.com (Damien Sandras) Date: Sat, 07 Feb 2009 17:37:43 +0100 Subject: [Ekiga-list] Revisited: visual feedback when making dbus/cli calls In-Reply-To: <498DAA8A.9080307@gmail.com> References: <498DAA8A.9080307@gmail.com> Message-ID: <1234024663.4242.18.camel@scorpion.multitel.be> Le samedi 07 f?vrier 2009 ? 16:36 +0100, Alec Leamas a ?crit : > I'm currently using the Dbus interface to establish Ekiga calls. The > basic functionality seems fine, but to my understanding there are some > glitches: > > - When making an ekiga.Call(uri)/ekiga.Show() sequence, the call > is indeed placed to the uri. Also, if there is no open window, > a main window is opened. In this the hook is off (red phone), but > the uri called is not reflected in the "dialpad" entry up-left. > Net result from a visual, user perspective is some kind of > "invisible" call (besides the history, where it eventually is > listed). > > - If the window is open already, it's likely to be hidden by other > windows. In this situation the Show() method seems to do nothing. > I think it would be more intuitive if the window popped up after > a Show() call instead of staying hidden in this situation. Is that Ekiga 3.0 ? You are free to propose patches. I will commit them... -- _ 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 Feb 7 16:39:48 2009 From: dsandras at seconix.com (Damien Sandras) Date: Sat, 07 Feb 2009 17:39:48 +0100 Subject: [Ekiga-list] Can not connect to echo server In-Reply-To: <498D957B.3070708@ifaz.de> References: <498C1666.9000006@ifaz.de> <1233999102.4242.6.camel@scorpion.multitel.be> <498D85DD.6090003@ifaz.de> <1234011994.4242.12.camel@scorpion.multitel.be> <498D8A30.1050608@ifaz.de> <1234015239.4242.14.camel@scorpion.multitel.be> <498D957B.3070708@ifaz.de> Message-ID: <1234024788.4242.21.camel@scorpion.multitel.be> Le samedi 07 f?vrier 2009 ? 15:06 +0100, Franz Fuder a ?crit : > Damien Sandras schrieb: > > Le samedi 07 f?vrier 2009 ? 14:18 +0100, Franz Fuder a ?crit : > > > > > > Perhaps you enabled all codecs with all options ? > > > > > > > > > > > Yes I have done, is this not correct ? Which one could I use ? > > > > > > > Just those you need... > > > Thanks for the tip, in the audio section all the codecs are fine. In > the video section only the h261 the first one is working. If I > activate one of the others it can not connect only with the h261 it > can connect wiht the server. The server supports all of them, but if you enable all of them at the same time, it is possible the SIP message becomes too big. Simply remove codecs you do not use. The defaults are actually a good choice. > I used the echo cancellation but when I use the USB Cam mic I get terrible echoes. The echo canceler only works well when the same device is used for recording and playing. That is the same with most commercial cancelers too. -- _ 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 mariofutire at googlemail.com Sat Feb 7 17:28:13 2009 From: mariofutire at googlemail.com (Andrea) Date: Sat, 07 Feb 2009 17:28:13 +0000 Subject: [Ekiga-list] Help debugging interoperability with Messenger Message-ID: Hi, I would like to ask help to understand why I cannot connect (any more) to Windows Messenger. I was able to connect audio/video using Ekiga 2.X, but today, first time I have tried with Ekiga 3.0.2 I cannot see video and audio is mute (same for them). I have attached the output of "ekiga -d 4", maybe there is something clear about what is wrong. I might be something completely unrelated, but the echo test works for both of us. Using Ekiga 2.x I used to have an issue whether PCMU was above or below PCMA (can't remember which way), but I have tried both and the result is the same. Thank you very much. Here is the log http://xoomer.alice.it/enodetti/log/ekiga.txt.gz Andrea From leamas.alec at gmail.com Sat Feb 7 19:11:40 2009 From: leamas.alec at gmail.com (Alec Leamas) Date: Sat, 07 Feb 2009 20:11:40 +0100 Subject: [Ekiga-list] Revisited: visual feedback when making dbus/cli calls In-Reply-To: <1234024663.4242.18.camel@scorpion.multitel.be> References: <498DAA8A.9080307@gmail.com> <1234024663.4242.18.camel@scorpion.multitel.be> Message-ID: <498DDCEC.4000605@gmail.com> Damien Sandras wrote: > Le samedi 07 f?vrier 2009 ? 16:36 +0100, Alec Leamas a ?crit : > >> I'm currently using the Dbus interface to establish Ekiga calls. The >> basic functionality seems fine, but to my understanding there are some >> glitches: >> >> - When making an ekiga.Call(uri)/ekiga.Show() sequence, the call >> is indeed placed to the uri. Also, if there is no open window, >> a main window is opened. In this the hook is off (red phone), but >> the uri called is not reflected in the "dialpad" entry up-left. >> Net result from a visual, user perspective is some kind of >> "invisible" call (besides the history, where it eventually is >> listed). >> >> - If the window is open already, it's likely to be hidden by other >> windows. In this situation the Show() method seems to do nothing. >> I think it would be more intuitive if the window popped up after >> a Show() call instead of staying hidden in this situation. >> > > Is that Ekiga 3.0 ? > 3.0.2 > You are free to propose patches. I will commit them... > It's quite a step to dive into the code. But I *am* tempted. Stay tuned... From raul at iem.cfmac.csic.es Sat Feb 7 21:10:49 2009 From: raul at iem.cfmac.csic.es (=?iso-8859-1?q?Ra=FAl_Z=2E?= =?iso-8859-1?q?_Mart=EDnez?=) Date: Sat, 7 Feb 2009 22:10:49 +0100 Subject: [Ekiga-list] Cannot answer calls (no popup window) Message-ID: <200902072210.49937.raul@iem.cfmac.csic.es> Hi everybody, I have found a strange problem with ekiga 3.0.1 and Opensuse 11.1. When I receive a call I can hear ekiga ringing, but the answer popup window which I was used to from earlier ekiga versions does not show up. Given that one cannot answer the call from the main ekiga window, the result is that I am unable to pick up. Initially I thought it must be a problem related to kde 4.2, which I am using in one of the computers... so I installed opensuse 11.1 again in a different computer, but this time using as default desktop kde 3.5. Same problem: ekiga 3.0.1 with kde 3.5 on opensuse 11.1 does not produce an "answer" window. I have tried upgrading to 3.0.2 with the same result. Anybody has experienced anything similar? I am thinking maybe the opensuse installation is missing some gnome library, but it is pure speculation. Thanks in advance! BA From avnet21 at hotmail.com Sat Feb 7 21:11:00 2009 From: avnet21 at hotmail.com (avnet21 at hotmail.com) Date: Sat, 7 Feb 2009 13:11:00 -0800 Subject: [Ekiga-list] =?utf-8?q?Respuesta_autom=C3=A1tica?= In-Reply-To: <200902072210.49937.raul@iem.cfmac.csic.es> Message-ID: An HTML attachment was scrubbed... URL: From dsandras at seconix.com Sat Feb 7 21:57:47 2009 From: dsandras at seconix.com (Damien Sandras) Date: Sat, 07 Feb 2009 22:57:47 +0100 Subject: [Ekiga-list] Cannot answer calls (no popup window) In-Reply-To: <200902072210.49937.raul@iem.cfmac.csic.es> References: <200902072210.49937.raul@iem.cfmac.csic.es> Message-ID: <1234043867.4606.4.camel@scorpion.multitel.be> Hi, Le samedi 07 f?vrier 2009 ? 22:10 +0100, Ra?l Z. Mart?nez a ?crit : > Hi everybody, > > I have found a strange problem with ekiga 3.0.1 and Opensuse 11.1. When I > receive a call I can hear ekiga ringing, but the answer popup window which I > was used to from earlier ekiga versions does not show up. Given that one > cannot answer the call from the main ekiga window, the result is that I am > unable to pick up. > > Initially I thought it must be a problem related to kde 4.2, which I am using > in one of the computers... so I installed opensuse 11.1 again in a different > computer, but this time using as default desktop kde 3.5. Same problem: ekiga > 3.0.1 with kde 3.5 on opensuse 11.1 does not produce an "answer" window. > > I have tried upgrading to 3.0.2 with the same result. Anybody has experienced > anything similar? I am thinking maybe the opensuse installation is missing > some gnome library, but it is pure speculation. > Ekiga 3.0.x can be compiled with libnotify support or without. If it is compiled with libnotify support, you get a nice notification in the notification area like in the following screenshot : http://gaim-libnotify.sourceforge.net/shot.jpg My guess is that Ekiga has been compiled with libnotify support, but for some reason, the notification can not be displayed. Try running it in a terminal, perhaps there are warnings that could lead you to a solution. -- _ 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 avnet21 at hotmail.com Sat Feb 7 21:58:06 2009 From: avnet21 at hotmail.com (avnet21 at hotmail.com) Date: Sat, 7 Feb 2009 13:58:06 -0800 Subject: [Ekiga-list] =?utf-8?q?Respuesta_autom=C3=A1tica?= In-Reply-To: <1234043867.4606.4.camel@scorpion.multitel.be> Message-ID: An HTML attachment was scrubbed... URL: From dsandras at seconix.com Sat Feb 7 22:00:32 2009 From: dsandras at seconix.com (Damien Sandras) Date: Sat, 07 Feb 2009 23:00:32 +0100 Subject: [Ekiga-list] Help debugging interoperability with Messenger In-Reply-To: References: Message-ID: <1234044032.4606.8.camel@scorpion.multitel.be> Le samedi 07 f?vrier 2009 ? 17:28 +0000, Andrea a ?crit : > I would like to ask help to understand why I cannot connect (any more) to Windows Messenger. > I was able to connect audio/video using Ekiga 2.X, but today, first time I have tried with Ekiga > 3.0.2 I cannot see video and audio is mute (same for them). > > I have attached the output of "ekiga -d 4", maybe there is something clear about what is wrong. > I might be something completely unrelated, but the echo test works for both of us. > > Using Ekiga 2.x I used to have an issue whether PCMU was above or below PCMA (can't remember which > way), but I have tried both and the result is the same. > > Thank you very much. > > Here is the log > > http://xoomer.alice.it/enodetti/log/ekiga.txt.gz I see that it asks to receive audio video on ports in the 506X range, but it receives nothing. It's possible that the STUN test goes wrong and that those ports it detects are not correct. Could you check if Ekiga 2.0.x also detects ports in the same range? You can see this in the INVITE, in the m=audio and m=video lines. -- _ 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 raul at iem.cfmac.csic.es Sat Feb 7 22:38:29 2009 From: raul at iem.cfmac.csic.es (=?iso-8859-1?q?Ra=FAl_Z=2E?= =?iso-8859-1?q?_Mart=EDnez?=) Date: Sat, 7 Feb 2009 23:38:29 +0100 Subject: [Ekiga-list] Cannot answer calls (no popup window) In-Reply-To: <1234043867.4606.4.camel@scorpion.multitel.be> References: <200902072210.49937.raul@iem.cfmac.csic.es> <1234043867.4606.4.camel@scorpion.multitel.be> Message-ID: <200902072338.29568.raul@iem.cfmac.csic.es> On Saturday 07 February 2009 22:57:47 you wrote: > Ekiga 3.0.x can be compiled with libnotify support or without. If it is > compiled with libnotify support, you get a nice notification in the > notification area like in the following screenshot : > http://gaim-libnotify.sourceforge.net/shot.jpg > > My guess is that Ekiga has been compiled with libnotify support, but for > some reason, the notification can not be displayed. > > Try running it in a terminal, perhaps there are warnings that could lead > you to a solution. Hi Damien, and thanks for the response. Sorry, I forgot to mention that I had already tried the terminal, and running ekiga in debug mode(s) also, but didn't see anything suspicious (lots of messages related to ALSA and the video, but nothing that looked like it could be related to this when I receive a call). Additionally, I just finished a new opensuse 11.1 installation in a laptop and the same thing happens yet again! I did it mostly because both of the previous installations were done in 64 bits processors and I wanted to try with the 32 bit version of the distribution. No difference. Btw, one of the ekiga installations was downloaded -as binaries- from ekiga.org, so I am pretty sure the problem has to be related to Suse's system installation, not ekiga itself. I am very puzzled by the fact that nobody else has reported this here or in SuSE forums. If I have managed to find this problem in 3 out of 3 installations with different hardware somebody else must have seen it with this distribution. I have found reports of people who have it working, though. Anyway, I'll keep trying. Thanks again. - BA - From bnc at astronomicalresearchaustralia.org Sun Feb 8 01:09:32 2009 From: bnc at astronomicalresearchaustralia.org (Brian) Date: Sun, 08 Feb 2009 11:09:32 +1000 Subject: [Ekiga-list] Cannot answer calls (no popup window) In-Reply-To: <200902072338.29568.raul@iem.cfmac.csic.es> References: <200902072210.49937.raul@iem.cfmac.csic.es> <1234043867.4606.4.camel@scorpion.multitel.be> <200902072338.29568.raul@iem.cfmac.csic.es> Message-ID: Hi, I have the same setup opensuse 11.1 and ekiga 3.0.1 and get the same problem. The difference in my case is that it varies, 1) I have had the popup occur click on it and answer the call as normal. 2) The ring occurs and no popup 3) the ring occurs and it is ringing for an extended time and then the pop occurs. I have never seen the notification box in the tray. Is there a setting for this? To be clear I do have the icon in the tray which normally shows a green circle. When I answer a call it shows a set of headphones. Is it supposed to show something else? Thanks, Brian On Sun, 08 Feb 2009 08:38:29 +1000, Ra?l Z. Mart?nez wrote: > On Saturday 07 February 2009 22:57:47 you wrote: > >> Ekiga 3.0.x can be compiled with libnotify support or without. If it is >> compiled with libnotify support, you get a nice notification in the >> notification area like in the following screenshot : >> http://gaim-libnotify.sourceforge.net/shot.jpg >> >> My guess is that Ekiga has been compiled with libnotify support, but for >> some reason, the notification can not be displayed. >> >> Try running it in a terminal, perhaps there are warnings that could lead >> you to a solution. > > > Hi Damien, and thanks for the response. > Sorry, I forgot to mention that I had already tried the terminal, and > running > ekiga in debug mode(s) also, but didn't see anything suspicious (lots of > messages related to ALSA and the video, but nothing that looked like it > could > be related to this when I receive a call). > > Additionally, I just finished a new opensuse 11.1 installation in a > laptop > and the same thing happens yet again! I did it mostly because both of the > previous installations were done in 64 bits processors and I wanted to > try > with the 32 bit version of the distribution. No difference. Btw, one of > the > ekiga installations was downloaded -as binaries- from ekiga.org, so I am > pretty sure the problem has to be related to Suse's system installation, > not > ekiga itself. > > I am very puzzled by the fact that nobody else has reported this here > or in > SuSE forums. If I have managed to find this problem in 3 out of 3 > installations with different hardware somebody else must have seen it > with > this distribution. I have found reports of people who have it working, > though. > Anyway, I'll keep trying. > > Thanks again. > > - BA - > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ From avnet21 at hotmail.com Sun Feb 8 01:36:31 2009 From: avnet21 at hotmail.com (avnet21 at hotmail.com) Date: Sat, 7 Feb 2009 17:36:31 -0800 Subject: [Ekiga-list] =?utf-8?q?Respuesta_autom=C3=A1tica?= In-Reply-To: Message-ID: An HTML attachment was scrubbed... URL: From dsandras at seconix.com Sun Feb 8 08:53:31 2009 From: dsandras at seconix.com (Damien Sandras) Date: Sun, 08 Feb 2009 09:53:31 +0100 Subject: [Ekiga-list] Cannot answer calls (no popup window) In-Reply-To: References: <200902072210.49937.raul@iem.cfmac.csic.es> <1234043867.4606.4.camel@scorpion.multitel.be> <200902072338.29568.raul@iem.cfmac.csic.es> Message-ID: <1234083211.4353.1.camel@scorpion.multitel.be> Le dimanche 08 f?vrier 2009 ? 11:09 +1000, Brian a ?crit : > Hi, > I have the same setup opensuse 11.1 and ekiga 3.0.1 and get the same > problem. > > The difference in my case is that it varies, > 1) I have had the popup occur click on it and answer the call as normal. > 2) The ring occurs and no popup > 3) the ring occurs and it is ringing for an extended time and then the pop > occurs. > > I have never seen the notification box in the tray. > Is there a setting for this? > To be clear I do have the icon in the tray which normally shows a green > circle. > When I answer a call it shows a set of headphones. > Is it supposed to show something else? It depends how it was compiled. I think both of you should report the bug to the SuSE distribution if it also occurs with the RPM provided by SuSE. (If you tell the binary comes from us, they will tell the problem is in the binary). -- _ 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 Sun Feb 8 09:45:08 2009 From: sevmek at free.fr (yannick) Date: Sun, 08 Feb 2009 10:45:08 +0100 Subject: [Ekiga-list] Hacking: ekiga-callto In-Reply-To: <1233998959.4242.3.camel@scorpion.multitel.be> References: <1233647706.3413.1298206689@webmail.messagingengine.com> <1233682734.18030.37.camel@achille> <1233686408.5192.1.camel@scorpion.multitel.be> <1233741347.19079.1298445445@webmail.messagingengine.com> <1233774520.4593.4.camel@scorpion.multitel.be> <1233850723.32479.1298726781@webmail.messagingengine.com> <498B717B.5000603@gmail.com> <1233998959.4242.3.camel@scorpion.multitel.be> Message-ID: <1234086308.22549.5.camel@achille> Le samedi 07 f?vrier 2009 ? 10:29 +0100, Damien Sandras a ?crit : > Le vendredi 06 f?vrier 2009 ? 00:08 +0100, Alec Leamas a ?crit : > > I've been busy some evenings creating scripts to make ekiga calls from > > web pages. I am at a point where I can click on any phone number in a > > web page to make ekiga call this number. > > > > Unfortunately, most "real" phone numbers are not given in the standard, > > international form. So I have faced the need to add missing countrycodes > > for numbers missing it. This implies a need to configure countrycode etc > > for the users. There is a simple form for this. > > > > If anyone is interested, the scripts are available as rpm and tar.gz > > packages at > > ftp://mumin.dnsalias.net/pub/ekiga-callto/ . Also, if anyone think it's > > worth the effort, > > some new localisations would be really nice. The README covers how to > > use the > > stuff. > > Thanks for this work! > > Yannick, could we link to this from the wiki together with the Ekiga.net > web buttons? Sure, i'll do this in a few hours. It really seems a great effort. Thank you Alec! From avnet21 at hotmail.com Sun Feb 8 09:45:37 2009 From: avnet21 at hotmail.com (avnet21 at hotmail.com) Date: Sun, 8 Feb 2009 01:45:37 -0800 Subject: [Ekiga-list] =?utf-8?q?Respuesta_autom=C3=A1tica?= In-Reply-To: <1234086308.22549.5.camel@achille> Message-ID: An HTML attachment was scrubbed... URL: From leamas.alec at gmail.com Sun Feb 8 11:15:23 2009 From: leamas.alec at gmail.com (Alec Leamas) Date: Sun, 08 Feb 2009 12:15:23 +0100 Subject: [Ekiga-list] Revisited: visual feedback when making dbus/cli calls Message-ID: <498EBECB.8050306@gmail.com> Sorry for threading issues; I cleaned my mailbox.... I've just compiled trunk. The status is somewhat different here: - When making a cli/dbus call the number is now displayed in the main window. Fixed, that is ;-) - I'm using metacity at the monent. In 3.0.2, when the main window was opened due to a call, it was always on top ; if it already was open and hidden it remained hidden, though. In trunk, even when a fresh window is opened, it is often opened *under* the window which has the focus (i. e., the window that initiated the call). In other words, it has become worse. I'll look at it, but this is really something for a WM wizard. Anyone out there? --alec From avnet21 at hotmail.com Sun Feb 8 11:15:38 2009 From: avnet21 at hotmail.com (avnet21 at hotmail.com) Date: Sun, 8 Feb 2009 03:15:38 -0800 Subject: [Ekiga-list] =?utf-8?q?Respuesta_autom=C3=A1tica?= In-Reply-To: <498EBECB.8050306@gmail.com> Message-ID: An HTML attachment was scrubbed... URL: From dsandras at seconix.com Sun Feb 8 16:36:34 2009 From: dsandras at seconix.com (Damien Sandras) Date: Sun, 08 Feb 2009 17:36:34 +0100 Subject: [Ekiga-list] Revisited: visual feedback when making dbus/cli calls In-Reply-To: <498EBECB.8050306@gmail.com> References: <498EBECB.8050306@gmail.com> Message-ID: <1234110994.4353.12.camel@scorpion.multitel.be> Le dimanche 08 f?vrier 2009 ? 12:15 +0100, Alec Leamas a ?crit : > Sorry for threading issues; I cleaned my mailbox.... > > I've just compiled trunk. The status is somewhat different here: > > - When making a cli/dbus call the number is now displayed in the main > window. Fixed, that is ;-) Good ! > - I'm using metacity at the monent. In 3.0.2, when the main window was > opened due to a call, it was always on top ; if it already was open and > hidden it remained hidden, though. In trunk, even when a fresh window > is opened, it is often opened *under* the window which has the focus > (i. e., the window that initiated the call). In other words, it has > become worse. > I'll look at it, but this is really something for a WM wizard. Anyone > out there? There should be a call to gtk_window_present somewhere in on_established_call in main.cpp. -- _ 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 mariofutire at googlemail.com Sun Feb 8 19:41:27 2009 From: mariofutire at googlemail.com (Andrea) Date: Sun, 08 Feb 2009 19:41:27 +0000 Subject: [Ekiga-list] Help debugging interoperability with Messenger In-Reply-To: <1234044032.4606.8.camel@scorpion.multitel.be> References: <1234044032.4606.8.camel@scorpion.multitel.be> Message-ID: Damien Sandras wrote: > Le samedi 07 f?vrier 2009 ? 17:28 +0000, Andrea a ?crit : >> I would like to ask help to understand why I cannot connect (any more) to Windows Messenger. >> I was able to connect audio/video using Ekiga 2.X, but today, first time I have tried with Ekiga >> 3.0.2 I cannot see video and audio is mute (same for them). >> >> I have attached the output of "ekiga -d 4", maybe there is something clear about what is wrong. >> I might be something completely unrelated, but the echo test works for both of us. >> >> Using Ekiga 2.x I used to have an issue whether PCMU was above or below PCMA (can't remember which >> way), but I have tried both and the result is the same. >> >> Thank you very much. >> >> Here is the log >> >> http://xoomer.alice.it/enodetti/log/ekiga.txt.gz > > I see that it asks to receive audio video on ports in the 506X range, > but it receives nothing. > > It's possible that the STUN test goes wrong and that those ports it > detects are not correct. > > Could you check if Ekiga 2.0.x also detects ports in the same range? > > You can see this in the INVITE, in the m=audio and m=video lines. > Thanks for the suggestion, but it turned to be a NAT issue (as usual). My friend changed a modem for a router so introducing a NAT. I discovered that Messenger cannot use STUN to traverse the NAT. Going back to the modem, everything worked (better than ekiga 2, which is great!). I guess asking for ideas how to solve the NAT issue for Messenger is Off-Topic here! I will force him to install ekiga-windows. Thanks From avnet21 at hotmail.com Sun Feb 8 19:41:55 2009 From: avnet21 at hotmail.com (avnet21 at hotmail.com) Date: Sun, 8 Feb 2009 11:41:55 -0800 Subject: [Ekiga-list] =?utf-8?q?Respuesta_autom=C3=A1tica?= In-Reply-To: Message-ID: An HTML attachment was scrubbed... URL: From dsandras at seconix.com Sun Feb 8 20:08:09 2009 From: dsandras at seconix.com (Damien Sandras) Date: Sun, 08 Feb 2009 21:08:09 +0100 Subject: [Ekiga-list] Help debugging interoperability with Messenger In-Reply-To: References: <1234044032.4606.8.camel@scorpion.multitel.be> Message-ID: <1234123689.4554.0.camel@scorpion.multitel.be> Le dimanche 08 f?vrier 2009 ? 19:41 +0000, Andrea a ?crit : > > I see that it asks to receive audio video on ports in the 506X range, > > but it receives nothing. > > > > It's possible that the STUN test goes wrong and that those ports it > > detects are not correct. > > > > Could you check if Ekiga 2.0.x also detects ports in the same range? > > > > You can see this in the INVITE, in the m=audio and m=video lines. > > > > Thanks for the suggestion, but it turned to be a NAT issue (as usual). > My friend changed a modem for a router so introducing a NAT. > I discovered that Messenger cannot use STUN to traverse the NAT. > Going back to the modem, everything worked (better than ekiga 2, which is great!). Ah thanks for the feedback! I'm happy it is not a bug we introduced :) -- _ 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 steig at bezeqint.net Mon Feb 9 00:08:16 2009 From: steig at bezeqint.net (Menasheh Steiglitz) Date: Mon, 9 Feb 2009 02:08:16 +0200 Subject: [Ekiga-list] disable console window? Message-ID: <1F6A7C6D-5EFE-48BF-BF89-BE1A78EDCCBD@bezeqint.net> How do I disable the console window that appears when starting Ekiga 3.0.1 beta for Windows? From Eugen.Dedu at pu-pm.univ-fcomte.fr Mon Feb 9 08:38:21 2009 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Mon, 09 Feb 2009 09:38:21 +0100 Subject: [Ekiga-list] disable console window? In-Reply-To: <1F6A7C6D-5EFE-48BF-BF89-BE1A78EDCCBD@bezeqint.net> References: <1F6A7C6D-5EFE-48BF-BF89-BE1A78EDCCBD@bezeqint.net> Message-ID: <498FEB7D.7000304@pu-pm.univ-fcomte.fr> Menasheh Steiglitz wrote: > How do I disable the console window that appears when starting Ekiga > 3.0.1 beta for Windows? It is not (yet) possible. -- Eugen From mike at cchtml.com Mon Feb 9 17:44:46 2009 From: mike at cchtml.com (Michael Cronenworth) Date: Mon, 09 Feb 2009 11:44:46 -0600 Subject: [Ekiga-list] disable console window? In-Reply-To: <498FEB7D.7000304@pu-pm.univ-fcomte.fr> References: <1F6A7C6D-5EFE-48BF-BF89-BE1A78EDCCBD@bezeqint.net> <498FEB7D.7000304@pu-pm.univ-fcomte.fr> Message-ID: <49906B8E.5040705@cchtml.com> -------- Original Message -------- Subject: Re: [Ekiga-list] disable console window? From: Eugen Dedu To: Ekiga mailing list Date: 02/09/2009 02:38 AM > > It is not (yet) possible. > If Ekiga for Windows is being built with mingw, then they need to add "-mwindows" to have it output a Windows application instead of a Console application. This is a two second Makefile and recompile. I'm not sure why they didn't compile it this way. If they are not using mingw... then I guess they are on their own. From sevmek at free.fr Mon Feb 9 18:13:48 2009 From: sevmek at free.fr (yannick) Date: Mon, 09 Feb 2009 19:13:48 +0100 Subject: [Ekiga-list] Hacking: ekiga-callto In-Reply-To: <1233998959.4242.3.camel@scorpion.multitel.be> References: <1233647706.3413.1298206689@webmail.messagingengine.com> <1233682734.18030.37.camel@achille> <1233686408.5192.1.camel@scorpion.multitel.be> <1233741347.19079.1298445445@webmail.messagingengine.com> <1233774520.4593.4.camel@scorpion.multitel.be> <1233850723.32479.1298726781@webmail.messagingengine.com> <498B717B.5000603@gmail.com> <1233998959.4242.3.camel@scorpion.multitel.be> Message-ID: <1234203228.8086.6.camel@achille> Le samedi 07 f?vrier 2009 ? 10:29 +0100, Damien Sandras a ?crit : > Le vendredi 06 f?vrier 2009 ? 00:08 +0100, Alec Leamas a ?crit : > > I've been busy some evenings creating scripts to make ekiga calls from > > web pages. I am at a point where I can click on any phone number in a > > web page to make ekiga call this number. > > > > Unfortunately, most "real" phone numbers are not given in the standard, > > international form. So I have faced the need to add missing countrycodes > > for numbers missing it. This implies a need to configure countrycode etc > > for the users. There is a simple form for this. > > > > If anyone is interested, the scripts are available as rpm and tar.gz > > packages at > > ftp://mumin.dnsalias.net/pub/ekiga-callto/ . Also, if anyone think it's > > worth the effort, > > some new localisations would be really nice. The README covers how to > > use the > > stuff. > > Thanks for this work! > > Yannick, could we link to this from the wiki together with the Ekiga.net > web buttons? Here it is: http://wiki.ekiga.org/index.php/Ekiga.net_VoIP_service_subscription#Ekiga_Web_integration Alec, I've a few questions for you: 1- Can you provide a screenshot ;) 2- Is there an official (i mean public) way to contact you for contributors? 2- It this application portable to windows? (Mac OS?) 3- What is the coding langage used ? From dsandras at seconix.com Mon Feb 9 18:17:15 2009 From: dsandras at seconix.com (Damien Sandras) Date: Mon, 09 Feb 2009 19:17:15 +0100 Subject: [Ekiga-list] disable console window? In-Reply-To: <49906B8E.5040705@cchtml.com> References: <1F6A7C6D-5EFE-48BF-BF89-BE1A78EDCCBD@bezeqint.net> <498FEB7D.7000304@pu-pm.univ-fcomte.fr> <49906B8E.5040705@cchtml.com> Message-ID: <1234203435.4312.0.camel@scorpion.multitel.be> Le lundi 09 f?vrier 2009 ? 11:44 -0600, Michael Cronenworth a ?crit : > -------- Original Message -------- > Subject: Re: [Ekiga-list] disable console window? > From: Eugen Dedu > To: Ekiga mailing list > Date: 02/09/2009 02:38 AM > > > > > It is not (yet) possible. > > > > If Ekiga for Windows is being built with mingw, then they need to add > "-mwindows" to have it output a Windows application instead of a Console > application. This is a two second Makefile and recompile. I'm not sure > why they didn't compile it this way. > > If they are not using mingw... then I guess they are on their own. We have no one to maintain the WIN32 version. Any taker ? -- _ 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 mike at cchtml.com Mon Feb 9 19:50:42 2009 From: mike at cchtml.com (Michael Cronenworth) Date: Mon, 09 Feb 2009 13:50:42 -0600 Subject: [Ekiga-list] disable console window? In-Reply-To: <1234203435.4312.0.camel@scorpion.multitel.be> References: <1F6A7C6D-5EFE-48BF-BF89-BE1A78EDCCBD@bezeqint.net> <498FEB7D.7000304@pu-pm.univ-fcomte.fr> <49906B8E.5040705@cchtml.com> <1234203435.4312.0.camel@scorpion.multitel.be> Message-ID: <49908912.7070902@cchtml.com> -------- Original Message -------- Subject: Re: [Ekiga-list] disable console window? From: Damien Sandras To: Ekiga mailing list Date: 02/09/2009 12:17 PM > > We have no one to maintain the WIN32 version. Any taker ? Uh... :P If all it involved was compiling and packaging then I wouldn't mind. I don't have time to actually do development. I'll checkout the source and mess around a bit. It'll be a few days or so before you'll hear back from me most likely. From dsandras at seconix.com Mon Feb 9 20:03:52 2009 From: dsandras at seconix.com (Damien Sandras) Date: Mon, 09 Feb 2009 21:03:52 +0100 Subject: [Ekiga-list] disable console window? In-Reply-To: <49908912.7070902@cchtml.com> References: <1F6A7C6D-5EFE-48BF-BF89-BE1A78EDCCBD@bezeqint.net> <498FEB7D.7000304@pu-pm.univ-fcomte.fr> <49906B8E.5040705@cchtml.com> <1234203435.4312.0.camel@scorpion.multitel.be> <49908912.7070902@cchtml.com> Message-ID: <1234209832.4312.7.camel@scorpion.multitel.be> Le lundi 09 f?vrier 2009 ? 13:50 -0600, Michael Cronenworth a ?crit : > -------- Original Message -------- > Subject: Re: [Ekiga-list] disable console window? > From: Damien Sandras > To: Ekiga mailing list > Date: 02/09/2009 12:17 PM > > > > > We have no one to maintain the WIN32 version. Any taker ? > > Uh... :P > > If all it involved was compiling and packaging then I wouldn't mind. I > don't have time to actually do development. I'll checkout the source and > mess around a bit. It'll be a few days or so before you'll hear back > from me most likely. That's enough... If you can also do reports about stability, then it is perfect. -- _ 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 Mon Feb 9 23:06:58 2009 From: leamas.alec at gmail.com (Alec Leamas) Date: Tue, 10 Feb 2009 00:06:58 +0100 Subject: [Ekiga-list] Hacking: ekiga-callto: update In-Reply-To: <1234203228.8086.6.camel@achille> References: <1233647706.3413.1298206689@webmail.messagingengine.com> <1233682734.18030.37.camel@achille> <1233686408.5192.1.camel@scorpion.multitel.be> <1233741347.19079.1298445445@webmail.messagingengine.com> <1233774520.4593.4.camel@scorpion.multitel.be> <1233850723.32479.1298726781@webmail.messagingengine.com> <498B717B.5000603@gmail.com> <1233998959.4242.3.camel@scorpion.multitel.be> <1234203228.8086.6.camel@achille> Message-ID: <4990B712.3020701@gmail.com> I have updated the packages, fixed numerous installation bugs, added Ubuntu installation docs ( in README). Same url: ftp://mumin.dnsalias.net/pub/ekiga-callto contains RPM:s and tar.gz Bear in mind that mumin.dnsalias.net is a home server, with a limited amount of 9's describing the availability ;-) Retry, that is, when it doesn't work. Answers below yannick wrote: > Le samedi 07 f?vrier 2009 ? 10:29 +0100, Damien Sandras a ?crit : > >> Le vendredi 06 f?vrier 2009 ? 00:08 +0100, Alec Leamas a ?crit : >> >>> I've been busy some evenings creating scripts to make ekiga calls from >>> web pages. I am at a point where I can click on any phone number in a >>> web page to make ekiga call this number. >>> >>> Unfortunately, most "real" phone numbers are not given in the standard, >>> international form. So I have faced the need to add missing countrycodes >>> for numbers missing it. This implies a need to configure countrycode etc >>> for the users. There is a simple form for this. >>> >>> If anyone is interested, the scripts are available as rpm and tar.gz >>> packages at >>> ftp://mumin.dnsalias.net/pub/ekiga-callto/ . Also, if anyone think it's >>> worth the effort, >>> some new localisations would be really nice. The README covers how to >>> use the >>> stuff. >>> >> Thanks for this work! >> >> Yannick, could we link to this from the wiki together with the Ekiga.net >> web buttons? >> > > Here it is: > http://wiki.ekiga.org/index.php/Ekiga.net_VoIP_service_subscription#Ekiga_Web_integration > > Alec, I've a few questions for you: > > 1- Can you provide a screenshot ;) > Well, I could, but it's sort of meaningless.. just a normal webpage. The trick is the "clickability" of the page, but this is not easy to show in a screenshot. But I see what you mean, thinking...have to think more. Maybe three pages, one without links, one with, and a third showing ekiga calling the link? > 2- Is there an official (i mean public) way to contact you for > contributors? > It's possible to upload things to ftp://mumin.dnsalias.net/pub/upload. And there is leamas.alec(at)gmail.com > 2- It this application portable to windows? (Mac OS > 3- What is the coding langage used ? > Most likely, yes., it's python and javascript. MacOS shoud definitely be OK. Not all window users have python in place, I guess. Among other things, it would be really nice with some more localisations. Just grab the po/en_GB.po file, fill in the 12 lines and submit them to me... --alec From lecan75228 at yahoo.com Tue Feb 10 03:05:20 2009 From: lecan75228 at yahoo.com (Can Le) Date: Mon, 9 Feb 2009 19:05:20 -0800 (PST) Subject: [Ekiga-list] stop send email to me Message-ID: <563162.92153.qm@web58004.mail.re3.yahoo.com> please stop send email to me thank you -------------- next part -------------- An HTML attachment was scrubbed... URL: From rbergfeld at gmail.com Tue Feb 10 03:09:18 2009 From: rbergfeld at gmail.com (Rick Bergfeld) Date: Mon, 9 Feb 2009 21:09:18 -0600 Subject: [Ekiga-list] Fedora Core 10 - Ekiga 3.0.2 registration timeout() In-Reply-To: <7c8767520902091902j7ad74d9du4ee4626799ab7970@mail.gmail.com> References: <7c8767520902091902j7ad74d9du4ee4626799ab7970@mail.gmail.com> Message-ID: <7c8767520902091909r25e4a0d8p8da2f4d5db9ecbdf@mail.gmail.com> I'm not sure what has changed. I was running FC8 with Ekiga 2.01 (I think) and I didn't have any issues. I upgraded to FC10 and Ekiga 3.0.2 and now I "Could not register sip:" error and "Could not connect to remote host". I think maybe I'm missing somthing? I just did the default install of FC10, so maybe something is missing. Any help is appreciated. link to output.txt http://docs.google.com/Doc?id=dcz353zw_84pndt2fq -------------- next part -------------- An HTML attachment was scrubbed... URL: From az_zahra96 at yahoo.com Tue Feb 10 03:19:58 2009 From: az_zahra96 at yahoo.com (Dian Rini) Date: Mon, 9 Feb 2009 19:19:58 -0800 (PST) Subject: [Ekiga-list] stop send email to me References: <563162.92153.qm@web58004.mail.re3.yahoo.com> Message-ID: <777689.4864.qm@web50512.mail.re2.yahoo.com> please stop send email to me thank you -------------- next part -------------- An HTML attachment was scrubbed... URL: From barf at barfone.serveftp.net Tue Feb 10 03:27:38 2009 From: barf at barfone.serveftp.net (barf) Date: Tue, 10 Feb 2009 16:27:38 +1300 Subject: [Ekiga-list] Fedora Core 10 - Ekiga 3.0.2 registration timeout() In-Reply-To: <7c8767520902091909r25e4a0d8p8da2f4d5db9ecbdf@mail.gmail.com> References: <7c8767520902091902j7ad74d9du4ee4626799ab7970@mail.gmail.com> <7c8767520902091909r25e4a0d8p8da2f4d5db9ecbdf@mail.gmail.com> Message-ID: <1234236458.7708.12.camel@designbox> On Mon, 2009-02-09 at 21:09 -0600, Rick Bergfeld wrote: > I'm not sure what has changed. I was running FC8 with Ekiga 2.01 (I > think) and I didn't have any issues. I upgraded to FC10 and Ekiga > 3.0.2 and now I "Could not register sip:" error and "Could not connect > to remote host". I think maybe I'm missing somthing? I just did the > default install of FC10, so maybe something is missing. Any help is > appreciated. > > link to output.txt http://docs.google.com/Doc?id=dcz353zw_84pndt2fq As a first port of call I'd check the firewall settings. > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list From joe at socallinuxexpo.org Tue Feb 10 03:45:40 2009 From: joe at socallinuxexpo.org (joe at socallinuxexpo.org) Date: Mon, 9 Feb 2009 19:45:40 -0800 (PST) Subject: [Ekiga-list] GNOME at the Socal Linux Expo Message-ID: <51763.75.19.166.49.1234237540.squirrel@socallinuxexpo.org> Hey guys, The Southern California Linux Expo, a community run conference taking place in Los Angeles on February 20th to 22nd, is offering a 50% discount to the Gnome community. When you go to register[1], just enter the promo code: GNOME. If you have any questions, please let me know. Thanks! Joe Smith Southern California Linux Expo [1] https://socallinuxexpo.org/reg7/ From leamas.alec at gmail.com Tue Feb 10 07:54:35 2009 From: leamas.alec at gmail.com (Alec Leamas) Date: Tue, 10 Feb 2009 08:54:35 +0100 Subject: [Ekiga-list] Hacking: ekiga-callto In-Reply-To: <1234086308.22549.5.camel@achille> References: <1233647706.3413.1298206689@webmail.messagingengine.com> <1233682734.18030.37.camel@achille> <1233686408.5192.1.camel@scorpion.multitel.be> <1233741347.19079.1298445445@webmail.messagingengine.com> <1233774520.4593.4.camel@scorpion.multitel.be> <1233850723.32479.1298726781@webmail.messagingengine.com> <498B717B.5000603@gmail.com> <1233998959.4242.3.camel@scorpion.multitel.be> <1234086308.22549.5.camel@achille> Message-ID: <499132BB.5020207@gmail.com> There are some "best effort" screenshots at ftp://mumin.dnsalias.net/pub/ekiga-callto/shots/. Anyone having a better idea how to present it? --alec From leamas.alec at gmail.com Tue Feb 10 08:13:43 2009 From: leamas.alec at gmail.com (Alec Leamas) Date: Tue, 10 Feb 2009 09:13:43 +0100 Subject: [Ekiga-list] Hacking: ekiga-callto: update In-Reply-To: <4990B712.3020701@gmail.com> References: <1233647706.3413.1298206689@webmail.messagingengine.com> <1233682734.18030.37.camel@achille> <1233686408.5192.1.camel@scorpion.multitel.be> <1233741347.19079.1298445445@webmail.messagingengine.com> <1233774520.4593.4.camel@scorpion.multitel.be> <1233850723.32479.1298726781@webmail.messagingengine.com> <498B717B.5000603@gmail.com> <1233998959.4242.3.camel@scorpion.multitel.be> <1234203228.8086.6.camel@achille> <4990B712.3020701@gmail.com> Message-ID: <49913737.8010609@gmail.com> Alec Leamas wrote: [cut] >> 2- It this application portable to windows? (Mac OS >> 3- What is the coding langage used ? >> > Most likely, yes., it's python and javascript. MacOS shoud definitely > be OK. Not all window users have python in place, I guess. > [cut] The dependencies are really gconf and gtk. Gconf should be replaced by the registry on windows, no idea of MacOS. Gtk is available also on windows, but I have really not the the feeling for whether is a good solution. Anyway, the GUI python code (ekiga-callto-config) is just ~100 lines. From Eugen.Dedu at pu-pm.univ-fcomte.fr Tue Feb 10 10:02:48 2009 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Tue, 10 Feb 2009 11:02:48 +0100 Subject: [Ekiga-list] Hacking: ekiga-callto: update In-Reply-To: <4990B712.3020701@gmail.com> References: <1233647706.3413.1298206689@webmail.messagingengine.com> <1233682734.18030.37.camel@achille> <1233686408.5192.1.camel@scorpion.multitel.be> <1233741347.19079.1298445445@webmail.messagingengine.com> <1233774520.4593.4.camel@scorpion.multitel.be> <1233850723.32479.1298726781@webmail.messagingengine.com> <498B717B.5000603@gmail.com> <1233998959.4242.3.camel@scorpion.multitel.be> <1234203228.8086.6.camel@achille> <4990B712.3020701@gmail.com> Message-ID: <499150C8.8080503@pu-pm.univ-fcomte.fr> About the phone number format, is http://wiki.ekiga.org/index.php/API::GmContact::PhoneNumbers useful to you? Eugen Alec Leamas wrote: > I have updated the packages, fixed numerous installation bugs, added > Ubuntu installation docs ( in README). > Same url: ftp://mumin.dnsalias.net/pub/ekiga-callto contains RPM:s and > tar.gz > > Bear in mind that mumin.dnsalias.net is a home server, with a limited > amount of 9's describing the availability ;-) Retry, that is, when it > doesn't work. > > Answers below > > yannick wrote: >> Le samedi 07 f?vrier 2009 ? 10:29 +0100, Damien Sandras a ?crit : >> >>> Le vendredi 06 f?vrier 2009 ? 00:08 +0100, Alec Leamas a ?crit : >>> >>>> I've been busy some evenings creating scripts to make ekiga calls >>>> from web pages. I am at a point where I can click on any phone >>>> number in a web page to make ekiga call this number. >>>> >>>> Unfortunately, most "real" phone numbers are not given in the >>>> standard, international form. So I have faced the need to add >>>> missing countrycodes for numbers missing it. This implies a need to >>>> configure countrycode etc for the users. There is a simple form for >>>> this. >>>> >>>> If anyone is interested, the scripts are available as rpm and tar.gz >>>> packages at >>>> ftp://mumin.dnsalias.net/pub/ekiga-callto/ . Also, if anyone think >>>> it's worth the effort, >>>> some new localisations would be really nice. The README covers how >>>> to use the >>>> stuff. >>>> >>> Thanks for this work! >>> >>> Yannick, could we link to this from the wiki together with the Ekiga.net >>> web buttons? >>> >> >> Here it is: >> http://wiki.ekiga.org/index.php/Ekiga.net_VoIP_service_subscription#Ekiga_Web_integration >> >> >> Alec, I've a few questions for you: >> >> 1- Can you provide a screenshot ;) >> > Well, I could, but it's sort of meaningless.. just a normal webpage. The > trick is the "clickability" of the page, but this is not easy to show in > a screenshot. But I see what you mean, thinking...have to think more. > Maybe three pages, one without links, one with, and a third showing > ekiga calling the link? >> 2- Is there an official (i mean public) way to contact you for >> contributors? >> > It's possible to upload things to ftp://mumin.dnsalias.net/pub/upload. > And there is leamas.alec(at)gmail.com >> 2- It this application portable to windows? (Mac OS >> 3- What is the coding langage used ? >> > Most likely, yes., it's python and javascript. MacOS shoud definitely be > OK. Not all window users have python in place, I guess. > > Among other things, it would be really nice with some more > localisations. Just grab the po/en_GB.po file, fill in the 12 lines and > submit them to me... From duncan.lithgow at gmail.com Tue Feb 10 12:02:25 2009 From: duncan.lithgow at gmail.com (Duncan Lithgow) Date: Tue, 10 Feb 2009 13:02:25 +0100 Subject: [Ekiga-list] stop send email to me In-Reply-To: <563162.92153.qm@web58004.mail.re3.yahoo.com> References: <563162.92153.qm@web58004.mail.re3.yahoo.com> Message-ID: Go to http://mail.gnome.org/mailman/listinfo/ekiga-list to take yourself off the list. Duncan 2009/2/10 Can Le : > please stop send email to me > thank you > > > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > From duncan.lithgow at gmail.com Tue Feb 10 12:02:50 2009 From: duncan.lithgow at gmail.com (Duncan Lithgow) Date: Tue, 10 Feb 2009 13:02:50 +0100 Subject: [Ekiga-list] stop send email to me In-Reply-To: <777689.4864.qm@web50512.mail.re2.yahoo.com> References: <563162.92153.qm@web58004.mail.re3.yahoo.com> <777689.4864.qm@web50512.mail.re2.yahoo.com> Message-ID: Go to http://mail.gnome.org/mailman/listinfo/ekiga-list to take yourself off the list. Duncan 2009/2/10 Dian Rini : > > please stop send email to me > thank you > > > > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > From leamas.alec at gmail.com Tue Feb 10 12:31:47 2009 From: leamas.alec at gmail.com (Alec Leamas) Date: Tue, 10 Feb 2009 13:31:47 +0100 Subject: [Ekiga-list] Hacking: ekiga-callto: update In-Reply-To: <499150C8.8080503@pu-pm.univ-fcomte.fr> References: <1233647706.3413.1298206689@webmail.messagingengine.com> <1233682734.18030.37.camel@achille> <1233686408.5192.1.camel@scorpion.multitel.be> <1233741347.19079.1298445445@webmail.messagingengine.com> <1233774520.4593.4.camel@scorpion.multitel.be> <1233850723.32479.1298726781@webmail.messagingengine.com> <498B717B.5000603@gmail.com> <1233998959.4242.3.camel@scorpion.multitel.be> <1234203228.8086.6.camel@achille> <4990B712.3020701@gmail.com> <499150C8.8080503@pu-pm.univ-fcomte.fr> Message-ID: <499173B3.6070601@gmail.com> Yes. Thanks! --alec Eugen Dedu wrote: > About the phone number format, is > http://wiki.ekiga.org/index.php/API::GmContact::PhoneNumbers useful to > you? > > Eugen > > Alec Leamas wrote: >> I have updated the packages, fixed numerous installation bugs, added >> Ubuntu installation docs ( in README). >> Same url: ftp://mumin.dnsalias.net/pub/ekiga-callto contains RPM:s >> and tar.gz >> >> Bear in mind that mumin.dnsalias.net is a home server, with a limited >> amount of 9's describing the availability ;-) Retry, that is, when it >> doesn't work. >> >> Answers below >> >> yannick wrote: >>> Le samedi 07 f?vrier 2009 ? 10:29 +0100, Damien Sandras a ?crit : >>> >>>> Le vendredi 06 f?vrier 2009 ? 00:08 +0100, Alec Leamas a ?crit : >>>> >>>>> I've been busy some evenings creating scripts to make ekiga calls >>>>> from web pages. I am at a point where I can click on any phone >>>>> number in a web page to make ekiga call this number. >>>>> >>>>> Unfortunately, most "real" phone numbers are not given in the >>>>> standard, international form. So I have faced the need to add >>>>> missing countrycodes for numbers missing it. This implies a need >>>>> to configure countrycode etc for the users. There is a simple form >>>>> for this. >>>>> >>>>> If anyone is interested, the scripts are available as rpm and >>>>> tar.gz packages at >>>>> ftp://mumin.dnsalias.net/pub/ekiga-callto/ . Also, if anyone think >>>>> it's worth the effort, >>>>> some new localisations would be really nice. The README covers >>>>> how to use the >>>>> stuff. >>>>> >>>> Thanks for this work! >>>> >>>> Yannick, could we link to this from the wiki together with the >>>> Ekiga.net >>>> web buttons? >>>> >>> >>> Here it is: >>> http://wiki.ekiga.org/index.php/Ekiga.net_VoIP_service_subscription#Ekiga_Web_integration >>> >>> >>> Alec, I've a few questions for you: >>> >>> 1- Can you provide a screenshot ;) >>> >> Well, I could, but it's sort of meaningless.. just a normal webpage. >> The trick is the "clickability" of the page, but this is not easy to >> show in a screenshot. But I see what you mean, thinking...have to >> think more. Maybe three pages, one without links, one with, and a >> third showing ekiga calling the link? >>> 2- Is there an official (i mean public) way to contact you for >>> contributors? >>> >> It's possible to upload things to >> ftp://mumin.dnsalias.net/pub/upload. And there is >> leamas.alec(at)gmail.com >>> 2- It this application portable to windows? (Mac OS >>> 3- What is the coding langage used ? >>> >> Most likely, yes., it's python and javascript. MacOS shoud definitely >> be OK. Not all window users have python in place, I guess. >> >> Among other things, it would be really nice with some more >> localisations. Just grab the po/en_GB.po file, fill in the 12 lines >> and submit them to me... > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list From rbergfeld at gmail.com Tue Feb 10 15:05:53 2009 From: rbergfeld at gmail.com (Rick Bergfeld) Date: Tue, 10 Feb 2009 09:05:53 -0600 Subject: [Ekiga-list] ekiga-list Digest, Vol 31, Issue 19 In-Reply-To: References: Message-ID: <7c8767520902100705q2ac86dc3ob7af8f3bbdfe7a12@mail.gmail.com> On Tue, Feb 10, 2009 at 6:00 AM, wrote: > Date: Tue, 10 Feb 2009 16:27:38 +1300 > From: barf > Subject: Re: [Ekiga-list] Fedora Core 10 - Ekiga 3.0.2 registration > timeout() > To: Ekiga mailing list > Message-ID: <1234236458.7708.12.camel at designbox> > Content-Type: text/plain > > On Mon, 2009-02-09 at 21:09 -0600, Rick Bergfeld wrote: > > I'm not sure what has changed. I was running FC8 with Ekiga 2.01 (I > > think) and I didn't have any issues. I upgraded to FC10 and Ekiga > > 3.0.2 and now I "Could not register sip:" error and "Could not connect > > to remote host". I think maybe I'm missing somthing? I just did the > > default install of FC10, so maybe something is missing. Any help is > > appreciated. > > > > link to output.txt http://docs.google.com/Doc?id=dcz353zw_84pndt2fq > > As a first port of call I'd check the firewall settings. > > > I forgot to mention that I disabled the firewall completely on FC10, but did not reboot. I also tried setting up port forwarding on my Linksys router. -------------- next part -------------- An HTML attachment was scrubbed... URL: From leamas.alec at gmail.com Tue Feb 10 17:24:04 2009 From: leamas.alec at gmail.com (Alec Leamas) Date: Tue, 10 Feb 2009 18:24:04 +0100 Subject: [Ekiga-list] ekiga-list Digest, Vol 31, Issue 19 In-Reply-To: <7c8767520902100705q2ac86dc3ob7af8f3bbdfe7a12@mail.gmail.com> References: <7c8767520902100705q2ac86dc3ob7af8f3bbdfe7a12@mail.gmail.com> Message-ID: <4991B834.3050902@gmail.com> Rick Bergfeld wrote: > > [cut] > > On Mon, 2009-02-09 at 21:09 -0600, Rick Bergfeld wrote: > > I'm not sure what has changed. I was running FC8 with Ekiga > 2.01 (I > > think) and I didn't have any issues. I upgraded to FC10 and Ekiga > > 3.0.2 and now I "Could not register sip:" error and "Could not > connect > > to remote host". I think maybe I'm missing somthing? I just > did the > > default install of FC10, so maybe something is missing. Any help is > > appreciated. > > > > link to output.txt http://docs.google.com/Doc?id=dcz353zw_84pndt2fq > > As a first port of call I'd check the firewall settings. > > > I forgot to mention that I disabled the firewall completely on FC10, > but did not reboot. I also tried setting up port forwarding on my > Linksys router. I had some similar issues as well, they were related to the combination of Ekiga and my router. Long story short: disabling stun made this to work for me. There is no UI for this, you have to patch directly into the gconf database: install the gconf-editor package, use it from Application | System Tools The path is /apps/ekiga/nat/disable_stun. If your router works like mine, disable all forwarding etc and let it handle sip in its own way. HTH --alec From rbergfeld at gmail.com Wed Feb 11 02:27:50 2009 From: rbergfeld at gmail.com (Rick Bergfeld) Date: Tue, 10 Feb 2009 20:27:50 -0600 Subject: [Ekiga-list] Fedora Core 10 - Ekiga 3.0.2 registration timeout() In-Reply-To: <7c8767520902091909r25e4a0d8p8da2f4d5db9ecbdf@mail.gmail.com> References: <7c8767520902091902j7ad74d9du4ee4626799ab7970@mail.gmail.com> <7c8767520902091909r25e4a0d8p8da2f4d5db9ecbdf@mail.gmail.com> Message-ID: <7c8767520902101827w18092b71md419e1da9479c2f9@mail.gmail.com> Here is a little more info on my issue. I completely disable the firewall and I still receive the same error. I took a packet capture from the time I start ekiga to the time I receive the timeout error. http://docs.google.com/Doc?id=dcz353zw_95f7zw9hj I filtered out quite a bit of mDNS entries (UDP port 5353) and I read somewhere that avahi uses this? I'm lost now. On Mon, Feb 9, 2009 at 9:09 PM, Rick Bergfeld wrote: > I'm not sure what has changed. I was running FC8 with Ekiga 2.01 (I think) > and I didn't have any issues. I upgraded to FC10 and Ekiga 3.0.2 and now I > "Could not register sip:" error and "Could not connect to remote host". I > think maybe I'm missing somthing? I just did the default install of FC10, > so maybe something is missing. Any help is appreciated. > > link to output.txt http://docs.google.com/Doc?id=dcz353zw_84pndt2fq -------------- next part -------------- An HTML attachment was scrubbed... URL: From chinku.linux at gmail.com Wed Feb 11 04:59:55 2009 From: chinku.linux at gmail.com (chaitanya mehandru) Date: Wed, 11 Feb 2009 10:29:55 +0530 Subject: [Ekiga-list] Ekiga 3 on KDE 8.04 compilation steps on wikipedia Message-ID: <24b40b2b0902102059m4032025bu32885c6a586416f6@mail.gmail.com> Hi, The steps for compiling Ekiga 3.0.2 on KDE 8.04 can now be found at the : http://wiki.ekiga.org/index.php/Compile_your_own_stable_Ekiga_version_3_on_Kubuntu_8.04 . Some error occur when using the webcam which I am trying to fix. Please try bring up ekiga and let me know any issues. It would be helpful for me to have any feedback and suggestions. Thanks, Chaitanya -------------- next part -------------- An HTML attachment was scrubbed... URL: From sevmek at free.fr Wed Feb 11 08:49:00 2009 From: sevmek at free.fr (yannick) Date: Wed, 11 Feb 2009 09:49:00 +0100 Subject: [Ekiga-list] Hacking: ekiga-callto In-Reply-To: <499132BB.5020207@gmail.com> References: <1233647706.3413.1298206689@webmail.messagingengine.com> <1233682734.18030.37.camel@achille> <1233686408.5192.1.camel@scorpion.multitel.be> <1233741347.19079.1298445445@webmail.messagingengine.com> <1233774520.4593.4.camel@scorpion.multitel.be> <1233850723.32479.1298726781@webmail.messagingengine.com> <498B717B.5000603@gmail.com> <1233998959.4242.3.camel@scorpion.multitel.be> <1234086308.22549.5.camel@achille> <499132BB.5020207@gmail.com> Message-ID: <1234342141.8248.15.camel@achille> Le mardi 10 f?vrier 2009 ? 08:54 +0100, Alec Leamas a ?crit : > There are some "best effort" screenshots at > ftp://mumin.dnsalias.net/pub/ekiga-callto/shots/. Anyone having a better > idea how to present it? I filled your software under the interoperability field for most visibility: http://wiki.ekiga.org/index.php/Ekiga_Interoperability#Web I removed it from ekiga.net as it does not belong there featurely wise. Best regards, Yannick From chinku.linux at gmail.com Wed Feb 11 09:07:02 2009 From: chinku.linux at gmail.com (chaitanya mehandru) Date: Wed, 11 Feb 2009 14:37:02 +0530 Subject: [Ekiga-list] Ekiga3.0.2: how to get 30fps on CIF resolution Message-ID: <24b40b2b0902110107q59e592bfrd852b9f3b90ca04d@mail.gmail.com> Hi, I have been using qcif size of image and observed ~30fps for the video. Now, if i switch to CIF resolution, fps goes down significantly. The no. of frames transmitted on both sides is still the same. But i need to get the received frames to 30fps. Using CIF resolution, is there a way to reach 30fps for received frames as well? Thanks, Chaitanya -------------- next part -------------- An HTML attachment was scrubbed... URL: From Eugen.Dedu at pu-pm.univ-fcomte.fr Wed Feb 11 10:36:10 2009 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Wed, 11 Feb 2009 11:36:10 +0100 Subject: [Ekiga-list] Ekiga 3 on KDE 8.04 compilation steps on wikipedia In-Reply-To: <24b40b2b0902102059m4032025bu32885c6a586416f6@mail.gmail.com> References: <24b40b2b0902102059m4032025bu32885c6a586416f6@mail.gmail.com> Message-ID: <4992AA1A.4000701@pu-pm.univ-fcomte.fr> chaitanya mehandru wrote: > Hi, The steps for compiling Ekiga 3.0.2 on KDE 8.04 can now be found at > the : > http://wiki.ekiga.org/index.php/Compile_your_own_stable_Ekiga_version_3_on_Kubuntu_8.04 For info, in ptlib your configure line d. ./configure --prefix=/usr --enable-plugins --enable-v4l2 --disable-oss is identical to d. ./configure --prefix=/usr -- Eugen From bbagger at gmail.com Wed Feb 11 10:49:05 2009 From: bbagger at gmail.com (Bent) Date: Wed, 11 Feb 2009 11:49:05 +0100 Subject: [Ekiga-list] Ekiga 3 on KDE 8.04 compilation steps on wikipedia In-Reply-To: <24b40b2b0902102059m4032025bu32885c6a586416f6@mail.gmail.com> References: <24b40b2b0902102059m4032025bu32885c6a586416f6@mail.gmail.com> Message-ID: <2e19719f0902110249v3e3ecc06x59e07a2f2abeb4f6@mail.gmail.com> Hi Chaitanya 2009/2/11 chaitanya mehandru : > ... > The steps for compiling Ekiga 3.0.2 on KDE 8.04 can now be found at the > ... How did you manage to get a version 8.04 of KDE. I - and I guess most of the rest of us - are on a version 4.1? /Bent From chinku.linux at gmail.com Wed Feb 11 10:56:04 2009 From: chinku.linux at gmail.com (chaitanya mehandru) Date: Wed, 11 Feb 2009 16:26:04 +0530 Subject: [Ekiga-list] Ekiga 3 on KDE 8.04 compilation steps on wikipedia In-Reply-To: <2e19719f0902110249v3e3ecc06x59e07a2f2abeb4f6@mail.gmail.com> References: <24b40b2b0902102059m4032025bu32885c6a586416f6@mail.gmail.com> <2e19719f0902110249v3e3ecc06x59e07a2f2abeb4f6@mail.gmail.com> Message-ID: <24b40b2b0902110256n4d38a9d0w7f76bcd6a6a61031@mail.gmail.com> Hi Bent, Sorry for misunderstanding, I mean to indicate KDE on Ubuntu 8.04. I had been using KDE 8.04 as many people wanted ekiga 3.0.2 on KDE in UBuntu 8.04. On Wed, Feb 11, 2009 at 4:19 PM, Bent wrote: > Hi Chaitanya > > 2009/2/11 chaitanya mehandru : > > ... > > The steps for compiling Ekiga 3.0.2 on KDE 8.04 can now be found at > the > > ... > How did you manage to get a version 8.04 of KDE. I - and I guess most > of the rest of us - are on a version 4.1? > > /Bent > _______________________________________________ > 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 chinku.linux at gmail.com Wed Feb 11 10:58:59 2009 From: chinku.linux at gmail.com (chaitanya mehandru) Date: Wed, 11 Feb 2009 16:28:59 +0530 Subject: [Ekiga-list] Ekiga 3 on KDE 8.04 compilation steps on wikipedia In-Reply-To: <4992AA1A.4000701@pu-pm.univ-fcomte.fr> References: <24b40b2b0902102059m4032025bu32885c6a586416f6@mail.gmail.com> <4992AA1A.4000701@pu-pm.univ-fcomte.fr> Message-ID: <24b40b2b0902110258n3245846du41535e8c3a86f6f2@mail.gmail.com> Hi, I agree with you. I saw the same line on wiki.ekiga.org for compiling ptlib. So, I preferred to write what is already mentioned. You may see yourself. BTW, thanks for the info. On Wed, Feb 11, 2009 at 4:06 PM, Eugen Dedu wrote: > chaitanya mehandru wrote: > >> Hi, The steps for compiling Ekiga 3.0.2 on KDE 8.04 can now be found at >> the : >> >> http://wiki.ekiga.org/index.php/Compile_your_own_stable_Ekiga_version_3_on_Kubuntu_8.04 >> > > For info, in ptlib your configure line > > d. ./configure --prefix=/usr --enable-plugins --enable-v4l2 --disable-oss > > is identical to > > d. ./configure --prefix=/usr > > -- > Eugen > _______________________________________________ > 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 huynhhayen at gmail.com Wed Feb 11 15:37:28 2009 From: huynhhayen at gmail.com (Heou) Date: Wed, 11 Feb 2009 10:37:28 -0500 Subject: [Ekiga-list] Support for use ekiga softphone Message-ID: <1234366648.8469.11.camel@ubuntu.ubuntu-domain> Dear all, I have a problem when I use the ekiga softphone. From Edit/Account, I add new account and check on the box in the first column, I receive a notice in the status column: Registration failed: timeout. And I cannot use it. Could anyone help me to fix this error? -- Thanks and Regards, Heou. From Eugen.Dedu at pu-pm.univ-fcomte.fr Wed Feb 11 15:51:23 2009 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Wed, 11 Feb 2009 16:51:23 +0100 Subject: [Ekiga-list] Support for use ekiga softphone In-Reply-To: <1234366648.8469.11.camel@ubuntu.ubuntu-domain> References: <1234366648.8469.11.camel@ubuntu.ubuntu-domain> Message-ID: <4992F3FB.4030004@pu-pm.univ-fcomte.fr> Heou wrote: > Dear all, > > I have a problem when I use the ekiga softphone. From Edit/Account, I > add new account and check on the box in the first column, I receive a > notice in the status column: Registration failed: timeout. > And I cannot use it. > Could anyone help me to fix this error? Could you restart ekiga? -- Eugen From mike at cchtml.com Wed Feb 11 16:04:48 2009 From: mike at cchtml.com (Michael Cronenworth) Date: Wed, 11 Feb 2009 10:04:48 -0600 Subject: [Ekiga-list] SIP server ekiga.org down? Message-ID: <4992F720.20906@cchtml.com> Is the SIP server ekiga.org not online right now? I am not able to login to Ekiga (Linux or Windows). This started last night after I successfully tested the Windows Ekiga build. I've tested from two different computers using two different ISPs. From dsandras at seconix.com Wed Feb 11 16:28:42 2009 From: dsandras at seconix.com (Damien Sandras) Date: Wed, 11 Feb 2009 17:28:42 +0100 Subject: [Ekiga-list] SIP server ekiga.org down? In-Reply-To: <4992F720.20906@cchtml.com> References: <4992F720.20906@cchtml.com> Message-ID: <1234369722.4391.50.camel@scorpion.multitel.be> Le mercredi 11 f?vrier 2009 ? 10:04 -0600, Michael Cronenworth a ?crit : > Is the SIP server ekiga.org not online right now? I am not able to login > to Ekiga (Linux or Windows). This started last night after I > successfully tested the Windows Ekiga build. > > I've tested from two different computers using two different ISPs. It's up again, it was crashed! -- _ 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 rbergfeld at gmail.com Thu Feb 12 00:43:59 2009 From: rbergfeld at gmail.com (Rick Bergfeld) Date: Wed, 11 Feb 2009 18:43:59 -0600 Subject: [Ekiga-list] ekiga-list Digest, Vol 31, Issue 20 In-Reply-To: References: Message-ID: <7c8767520902111643i2d6a6ad0l1734ad38708806c9@mail.gmail.com> > > Rick Bergfeld wrote: > > > > [cut] > > > > On Mon, 2009-02-09 at 21:09 -0600, Rick Bergfeld wrote: > > > I'm not sure what has changed. I was running FC8 with Ekiga > > 2.01 (I > > > think) and I didn't have any issues. I upgraded to FC10 and Ekiga > > > 3.0.2 and now I "Could not register sip:" error and "Could not > > connect > > > to remote host". I think maybe I'm missing somthing? I just > > did the > > > default install of FC10, so maybe something is missing. Any help > is > > > appreciated. > > > > > > link to output.txt > http://docs.google.com/Doc?id=dcz353zw_84pndt2fq > > > > As a first port of call I'd check the firewall settings. > > > > > > I forgot to mention that I disabled the firewall completely on FC10, > > but did not reboot. I also tried setting up port forwarding on my > > Linksys router. > I had some similar issues as well, they were related to the combination > of Ekiga and my router. Long story short: disabling stun made this to > work for me. There is no UI for this, you have to patch directly into > the gconf database: install the gconf-editor package, use it from > Application | System Tools > The path is /apps/ekiga/nat/disable_stun. If your router works like > mine, disable all forwarding etc and let it handle sip in its own way. > > HTH > > --alec > > Thanks for the input. I don't have the exact key you mentioned. I do have /apps/ekiga/general/nat/ and created a boolean key disable_stun with a value of true but that doesn't turn off stun. It's still trying to use it. I tried leaving the stun server field blank and didn't get much further. I put my pc in the DMZ zone on the router and now I'm getting a 401 unauthorized error during my capture as well as an unreachable, yet I can ping the address. No. Time Source Destination Protocol Info 10 0.594155 192.168.0.200 86.64.162.35 SIP Request: REGISTER sip:ekiga.net Frame 10 (612 bytes on wire, 612 bytes captured) Ethernet II, Src: IntelCor_02:40:ca (00:1b:77:02:40:ca), Dst: Cisco-Li_1b:cb:a7 (00:16:b6:1b:cb:a7) Internet Protocol, Src: 192.168.0.200 (192.168.0.200), Dst: 86.64.162.35 (86.64.162.35) User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060) Session Initiation Protocol No. Time Source Destination Protocol Info 11 0.729206 86.64.162.35 192.168.0.200 SIP Status: 401 Unauthorized (0 bindings) Frame 11 (573 bytes on wire, 573 bytes captured) Ethernet II, Src: Cisco-Li_1b:cb:a7 (00:16:b6:1b:cb:a7), Dst: IntelCor_02:40:ca (00:1b:77:02:40:ca) Internet Protocol, Src: 86.64.162.35 (86.64.162.35), Dst: 192.168.0.200 (192.168.0.200) User Datagram Protocol, Src Port: sip (5060), Dst Port: 11935 (11935) Session Initiation Protocol No. Time Source Destination Protocol Info 12 0.729270 192.168.0.200 86.64.162.35 ICMP Destination unreachable (Port unreachable) -------------- next part -------------- An HTML attachment was scrubbed... URL: From chinku.linux at gmail.com Fri Feb 13 06:43:52 2009 From: chinku.linux at gmail.com (chaitanya mehandru) Date: Fri, 13 Feb 2009 12:13:52 +0530 Subject: [Ekiga-list] Dump FPS from ekiga 3.0.2 to a file Message-ID: <24b40b2b0902122243p490da840p2a14585f7f6b8bdf@mail.gmail.com> Hi, Is there a way to record the FPS from ekiga and dump it to a file for taking an average FPS reading? Thanks, Chaitanya -------------- next part -------------- An HTML attachment was scrubbed... URL: From blino at mandriva.org Fri Feb 13 17:35:43 2009 From: blino at mandriva.org (Olivier Blin) Date: Fri, 13 Feb 2009 18:35:43 +0100 Subject: [Ekiga-list] ekiga 3 and 16bpp displays Message-ID: Hello, I have a crash with ekiga (3.0.x or 3.1.x) when using a 16bpp display. Here is an interesting pointer in the trace: Could not find visual with colordepth of 24 bits per pixel It seems that XWindow::checkDepth() fallbacks to 24bpp, but it does not support 16bpp. The log + trace can be found here: http://people.mandriva.com/~blino/ekiga-crash-16bpp.log Is ekiga supposed to work with only 24bpp and 32bpp displays? What can be done to make it work on 16bpp displays? Thanks in advance -- Olivier Blin (blino) - Mandriva From wolfram.wagner at web.de Fri Feb 13 20:46:22 2009 From: wolfram.wagner at web.de (Wolfram Wagner) Date: Fri, 13 Feb 2009 21:46:22 +0100 Subject: [Ekiga-list] Fedora Core 10 - Ekiga 3.0.2 registration timeout() In-Reply-To: <7c8767520902101827w18092b71md419e1da9479c2f9@mail.gmail.com> References: <7c8767520902091902j7ad74d9du4ee4626799ab7970@mail.gmail.com> <7c8767520902091909r25e4a0d8p8da2f4d5db9ecbdf@mail.gmail.com> <7c8767520902101827w18092b71md419e1da9479c2f9@mail.gmail.com> Message-ID: <200902132146.22555.wolfram.wagner@web.de> Hello Rick, I am using Ekiga under Fedora 10 successful. (Besides some sporadic problems with my router.) If you want to see, what is going on, use wireshark: Start a recording session, filter the packages using the sip server of ekiga and look into the SIP packages! You can also run ekiga with options: ekiga -d 4 (but it is hard to analyse, because of the amount and depth in detail.) As I installed Fedora I had a registration problem too. I am not sure what it fixed. I remember that I re-created the account settings for my ekiga account. But maybe something else fixed it. As a last messure I would try: (Write down your Ekiga settings and accounts, as this will delete them!) Maybe it helps to install gconf-editor, start it USING YOUR NON-ROOT account and delete Apps/Ekiga completely. With next start, you get the default settings and you start clean... You will have to enter everything again! I warned you! If you make a mistake you still can 'yum reinstall ekiga'... Wolfram Am Mittwoch 11 Februar 2009 03:27:50 schrieb Rick Bergfeld: > Here is a little more info on my issue. I completely disable the firewall > and I still receive the same error. I took a packet capture from the time > I start ekiga to the time I receive the timeout error. > http://docs.google.com/Doc?id=dcz353zw_95f7zw9hj > I filtered out quite a bit of mDNS entries (UDP port 5353) and I read > somewhere that avahi uses this? I'm lost now. > > On Mon, Feb 9, 2009 at 9:09 PM, Rick Bergfeld wrote: > > I'm not sure what has changed. I was running FC8 with Ekiga 2.01 (I > > think) and I didn't have any issues. I upgraded to FC10 and Ekiga 3.0.2 > > and now I "Could not register sip:" error and "Could not connect to > > remote host". I think maybe I'm missing somthing? I just did the > > default install of FC10, so maybe something is missing. Any help is > > appreciated. > > > > link to output.txt http://docs.google.com/Doc?id=dcz353zw_84pndt2fq From Ekiga at 0x1b.com Fri Feb 13 23:15:26 2009 From: Ekiga at 0x1b.com (Ed) Date: Fri, 13 Feb 2009 16:15:26 -0700 Subject: [Ekiga-list] Fedora Core 10 - Ekiga 3.0.2 registration timeout() In-Reply-To: <200902132146.22555.wolfram.wagner@web.de> References: <7c8767520902091902j7ad74d9du4ee4626799ab7970@mail.gmail.com> <7c8767520902091909r25e4a0d8p8da2f4d5db9ecbdf@mail.gmail.com> <7c8767520902101827w18092b71md419e1da9479c2f9@mail.gmail.com> <200902132146.22555.wolfram.wagner@web.de> Message-ID: <6e30f6790902131515x50430d73ne33dc998687fe8f1@mail.gmail.com> On Fri, Feb 13, 2009 at 1:46 PM, Wolfram Wagner wrote: > Hello Rick, > I am using Ekiga under Fedora 10 successful. (Besides some sporadic problems > with my router.) > > If you want to see, what is going on, use wireshark: > Start a recording session, filter the packages using the sip server of ekiga > and look into the SIP packages! You can also run ekiga with options: > ekiga -d 4 > (but it is hard to analyse, because of the amount and depth in detail.) > > As I installed Fedora I had a registration problem too. I am not sure what it > fixed. I remember that I re-created the account settings for my ekiga account. > But maybe something else fixed it. > > As a last messure I would try: (Write down your Ekiga settings and accounts, > as this will delete them!) > Maybe it helps to install gconf-editor, start it USING YOUR NON-ROOT account > and delete Apps/Ekiga completely. With next start, you get the default > settings and you start clean... > You will have to enter everything again! I warned you! > > If you make a mistake you still can 'yum reinstall ekiga'... > > Wolfram > > Am Mittwoch 11 Februar 2009 03:27:50 schrieb Rick Bergfeld: >> Here is a little more info on my issue. I completely disable the firewall >> and I still receive the same error. I took a packet capture from the time >> I start ekiga to the time I receive the timeout error. >> http://docs.google.com/Doc?id=dcz353zw_95f7zw9hj >> I filtered out quite a bit of mDNS entries (UDP port 5353) and I read >> somewhere that avahi uses this? I'm lost now. >> >> On Mon, Feb 9, 2009 at 9:09 PM, Rick Bergfeld wrote: >> > I'm not sure what has changed. I was running FC8 with Ekiga 2.01 (I >> > think) and I didn't have any issues. I upgraded to FC10 and Ekiga 3.0.2 >> > and now I "Could not register sip:" error and "Could not connect to >> > remote host". I think maybe I'm missing somthing? I just did the >> > default install of FC10, so maybe something is missing. Any help is >> > appreciated. >> > >> > link to output.txt http://docs.google.com/Doc?id=dcz353zw_84pndt2fq > Fedora 10 got all enthusiastic with SELinux maybe? You might toggle SELinux in & out of permissive mode while you're in flipin'-switches mode. man setenforce & sestatus ymmv From bas.driessen at xobas.com Sat Feb 14 00:48:19 2009 From: bas.driessen at xobas.com (Bas Driessen) Date: Sat, 14 Feb 2009 10:48:19 +1000 Subject: [Ekiga-list] Problems incoming calls. Message-ID: <1234572499.4794.11.camel@ams.xobas.net> Hello, I am using Ekiga 3.0.2 on Fedora 10 x86_64 (64 bit). I have a VoIP account with my internet provider and I have setup Ekiga to use that and that all works fine. However, within a couple of minutes, the incoming calls do not work anymore. It goes straight to the voice mail. If I de-register and register again, all works again for a minute or 2 and then same problem. Outgoing calls are fine and stable. What can be a possible cause and/or what can I do to further investigate. To eliminate the fact that it is not a router/infrastructure etc issue, I have tested with Twinkle. This package seems stable both incoming as outgoing. So the issue appears to be with Ekiga. How can I see how I am registered in Ekiga? I want to see something like this: ;q=0.500;expires=360. As outgoing calls still work, registration must perhaps get confused somehow and change to something like: ;q=0.500;expires=360 (I am only guessing) meaning that I am still connected to a sip server, but not linked anymore to the incoming number. Any ideas/tips/hints/solutions are appreciated. Thanks, Bas. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mike at cchtml.com Sat Feb 14 00:55:34 2009 From: mike at cchtml.com (Michael Cronenworth) Date: Fri, 13 Feb 2009 18:55:34 -0600 Subject: [Ekiga-list] Fedora Core 10 - Ekiga 3.0.2 registration timeout() In-Reply-To: <6e30f6790902131515x50430d73ne33dc998687fe8f1@mail.gmail.com> References: <7c8767520902091902j7ad74d9du4ee4626799ab7970@mail.gmail.com> <7c8767520902091909r25e4a0d8p8da2f4d5db9ecbdf@mail.gmail.com> <7c8767520902101827w18092b71md419e1da9479c2f9@mail.gmail.com> <200902132146.22555.wolfram.wagner@web.de> <6e30f6790902131515x50430d73ne33dc998687fe8f1@mail.gmail.com> Message-ID: <49961686.3060802@cchtml.com> Ed wrote: > Fedora 10 got all enthusiastic with SELinux maybe? > You might toggle SELinux in & out of permissive mode while you're in > flipin'-switches mode. > man setenforce & sestatus > ymmv > I'm using Ekiga 3.0.2 and Fedora 10 with SELinux in Enforced mode. I have no issues. In fact, I haven't had a single SELinux related issue since Fedora 9. I've been in enforced mode for almost a year now. If you do run into a problem there is a graphical tool that notifies you of SELinux denials and offers suggestions on workarounds. You can drop the SELinux jokes. -------------- next part -------------- An HTML attachment was scrubbed... URL: From bas.driessen at xobas.com Sat Feb 14 01:01:26 2009 From: bas.driessen at xobas.com (Bas Driessen) Date: Sat, 14 Feb 2009 11:01:26 +1000 Subject: [Ekiga-list] Fedora Core 10 - Ekiga 3.0.2 registration timeout() In-Reply-To: <49961686.3060802@cchtml.com> References: <7c8767520902091902j7ad74d9du4ee4626799ab7970@mail.gmail.com> <7c8767520902091909r25e4a0d8p8da2f4d5db9ecbdf@mail.gmail.com> <7c8767520902101827w18092b71md419e1da9479c2f9@mail.gmail.com> <200902132146.22555.wolfram.wagner@web.de> <6e30f6790902131515x50430d73ne33dc998687fe8f1@mail.gmail.com> <49961686.3060802@cchtml.com> Message-ID: <1234573286.4794.13.camel@ams.xobas.net> On Fri, 2009-02-13 at 18:55 -0600, Michael Cronenworth wrote: > Ed wrote: > > > > > > > Fedora 10 got all enthusiastic with SELinux maybe? > > You might toggle SELinux in & out of permissive mode while you're in > > flipin'-switches mode. > > man setenforce & sestatus > > ymmv > > > > > I'm using Ekiga 3.0.2 and Fedora 10 with SELinux in Enforced mode. I > have no issues. > > In fact, I haven't had a single SELinux related issue since Fedora 9. > I've been in enforced mode for almost a year now. If you do run into a > problem there is a graphical tool that notifies you of SELinux denials > and offers suggestions on workarounds. You can drop the SELinux > jokes. I have SELinux disabled, so that should not come into play. Same with iptables (firewall), disabled as well. Thanks for response. -------------- next part -------------- An HTML attachment was scrubbed... URL: From bas.driessen at xobas.com Sat Feb 14 01:02:14 2009 From: bas.driessen at xobas.com (Bas Driessen) Date: Sat, 14 Feb 2009 11:02:14 +1000 Subject: [Ekiga-list] Fedora Core 10 - Ekiga 3.0.2 registration timeout() In-Reply-To: <1234573286.4794.13.camel@ams.xobas.net> References: <7c8767520902091902j7ad74d9du4ee4626799ab7970@mail.gmail.com> <7c8767520902091909r25e4a0d8p8da2f4d5db9ecbdf@mail.gmail.com> <7c8767520902101827w18092b71md419e1da9479c2f9@mail.gmail.com> <200902132146.22555.wolfram.wagner@web.de> <6e30f6790902131515x50430d73ne33dc998687fe8f1@mail.gmail.com> <49961686.3060802@cchtml.com> <1234573286.4794.13.camel@ams.xobas.net> Message-ID: <1234573334.4794.14.camel@ams.xobas.net> oops .... please ignore below. Responded to wrong message ..... apologies. On Sat, 2009-02-14 at 11:01 +1000, Bas Driessen wrote: > > > On Fri, 2009-02-13 at 18:55 -0600, Michael Cronenworth wrote: > > > Ed wrote: > > > > > Fedora 10 got all enthusiastic with SELinux maybe? > > > You might toggle SELinux in & out of permissive mode while you're in > > > flipin'-switches mode. > > > man setenforce & sestatus > > > ymmv > > > > > > > > > > > > > > > I'm using Ekiga 3.0.2 and Fedora 10 with SELinux in Enforced mode. I > > have no issues. > > > > In fact, I haven't had a single SELinux related issue since Fedora > > 9. I've been in enforced mode for almost a year now. If you do run > > into a problem there is a graphical tool that notifies you of > > SELinux denials and offers suggestions on workarounds. You can drop > > the SELinux jokes. > > > I have SELinux disabled, so that should not come into play. Same with > iptables (firewall), disabled as well. > > Thanks for response. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Eugen.Dedu at pu-pm.univ-fcomte.fr Sat Feb 14 10:30:42 2009 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Sat, 14 Feb 2009 11:30:42 +0100 Subject: [Ekiga-list] Dump FPS from ekiga 3.0.2 to a file In-Reply-To: <24b40b2b0902122243p490da840p2a14585f7f6b8bdf@mail.gmail.com> References: <24b40b2b0902122243p490da840p2a14585f7f6b8bdf@mail.gmail.com> Message-ID: <49969D52.5040603@pu-pm.univ-fcomte.fr> chaitanya mehandru wrote: > Hi, Is there a way to record the FPS from ekiga and dump it to a file for > taking an average FPS reading? I think the only solution is to modify the ekiga code yourself. -- Eugen From dsandras at seconix.com Sat Feb 14 10:38:40 2009 From: dsandras at seconix.com (Damien Sandras) Date: Sat, 14 Feb 2009 11:38:40 +0100 Subject: [Ekiga-list] Problems incoming calls. In-Reply-To: <1234572499.4794.11.camel@ams.xobas.net> References: <1234572499.4794.11.camel@ams.xobas.net> Message-ID: <1234607920.4280.2.camel@scorpion.multitel.be> Le samedi 14 f?vrier 2009 ? 10:48 +1000, Bas Driessen a ?crit : > Hello, > > I am using Ekiga 3.0.2 on Fedora 10 x86_64 (64 bit). I have a VoIP > account with my internet provider and I have setup Ekiga to use that > and that all works fine. However, within a couple of minutes, the > incoming calls do not work anymore. It goes straight to the voice > mail. If I de-register and register again, all works again for a > minute or 2 and then same problem. Outgoing calls are fine and stable. > > What can be a possible cause and/or what can I do to further > investigate. To eliminate the fact that it is not a > router/infrastructure etc issue, I have tested with Twinkle. This > package seems stable both incoming as outgoing. So the issue appears > to be with Ekiga. > > How can I see how I am registered in Ekiga? I want to see something > like this: ;q=0.500;expires=360. As > outgoing calls still work, registration must perhaps get confused > somehow and change to something like: > ;q=0.500;expires=360 (I am only > guessing) meaning that I am still connected to a sip server, but not > linked anymore to the incoming number. > > Any ideas/tips/hints/solutions are appreciated. Perhaps the NAT binding on the router is closed. We send a 'probe' every 10 seconds to keep it alive. Perhaps you could try sending a probe every 3 seconds. To change this, you can edit the following key : /apps/ekiga/protocols/sip/binding_timeout using gconftool or gconf-editor. Do not edit the config files manually, it won't 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 dsandras at seconix.com Sat Feb 14 10:41:42 2009 From: dsandras at seconix.com (Damien Sandras) Date: Sat, 14 Feb 2009 11:41:42 +0100 Subject: [Ekiga-list] ekiga 3 and 16bpp displays In-Reply-To: References: Message-ID: <1234608102.4280.4.camel@scorpion.multitel.be> Le vendredi 13 f?vrier 2009 ? 18:35 +0100, Olivier Blin a ?crit : > Hello, > > I have a crash with ekiga (3.0.x or 3.1.x) when using a 16bpp display. > Here is an interesting pointer in the trace: > Could not find visual with colordepth of 24 bits per pixel > > It seems that XWindow::checkDepth() fallbacks to 24bpp, but it does not > support 16bpp. > > The log + trace can be found here: > http://people.mandriva.com/~blino/ekiga-crash-16bpp.log > > Is ekiga supposed to work with only 24bpp and 32bpp displays? I think so yes. > What can be done to make it work on 16bpp displays? Fix the code so that it works with 16bpp too :-) But is 16bpp that common ? -- _ 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 bas.driessen at xobas.com Sat Feb 14 13:06:26 2009 From: bas.driessen at xobas.com (Bas Driessen) Date: Sat, 14 Feb 2009 23:06:26 +1000 Subject: [Ekiga-list] Problems incoming calls. In-Reply-To: <1234607920.4280.2.camel@scorpion.multitel.be> References: <1234572499.4794.11.camel@ams.xobas.net> <1234607920.4280.2.camel@scorpion.multitel.be> Message-ID: <1234616786.3912.2.camel@ams.xobas.net> On Sat, 2009-02-14 at 11:38 +0100, Damien Sandras wrote: > Le samedi 14 f?vrier 2009 ? 10:48 +1000, Bas Driessen a ?crit : > > Hello, > > > > I am using Ekiga 3.0.2 on Fedora 10 x86_64 (64 bit). I have a VoIP > > account with my internet provider and I have setup Ekiga to use that > > and that all works fine. However, within a couple of minutes, the > > incoming calls do not work anymore. It goes straight to the voice > > mail. If I de-register and register again, all works again for a > > minute or 2 and then same problem. Outgoing calls are fine and stable. > > > > What can be a possible cause and/or what can I do to further > > investigate. To eliminate the fact that it is not a > > router/infrastructure etc issue, I have tested with Twinkle. This > > package seems stable both incoming as outgoing. So the issue appears > > to be with Ekiga. > > > > How can I see how I am registered in Ekiga? I want to see something > > like this: ;q=0.500;expires=360. As > > outgoing calls still work, registration must perhaps get confused > > somehow and change to something like: > > ;q=0.500;expires=360 (I am only > > guessing) meaning that I am still connected to a sip server, but not > > linked anymore to the incoming number. > > > > Any ideas/tips/hints/solutions are appreciated. > > Perhaps the NAT binding on the router is closed. > > We send a 'probe' every 10 seconds to keep it alive. > > Perhaps you could try sending a probe every 3 seconds. To change this, > you can edit the following key : > /apps/ekiga/protocols/sip/binding_timeout > using gconftool or gconf-editor. > > Do not edit the config files manually, it won't work. Thanks Damien. Tried that, but it did not work unfortunately. Fedora release ekiga-3.0.2-2.fc10 update yesterday. Updated and also no change. Is it possible that the problem is on the provider site? If so, which value/setting should I ask them to set/use? Anything else in Ekiga I can set. Proxy for instance? Can I edit STUN settings in Ekiga? Any other ideas? Thanks again. Bas. -------------- next part -------------- An HTML attachment was scrubbed... URL: From bas.driessen at xobas.com Sat Feb 14 13:26:18 2009 From: bas.driessen at xobas.com (Bas Driessen) Date: Sat, 14 Feb 2009 23:26:18 +1000 Subject: [Ekiga-list] Problems incoming calls. In-Reply-To: <1234607920.4280.2.camel@scorpion.multitel.be> References: <1234572499.4794.11.camel@ams.xobas.net> <1234607920.4280.2.camel@scorpion.multitel.be> Message-ID: <1234617978.3912.3.camel@ams.xobas.net> On Sat, 2009-02-14 at 11:38 +0100, Damien Sandras wrote: > Le samedi 14 f?vrier 2009 ? 10:48 +1000, Bas Driessen a ?crit : > > Hello, > > > > I am using Ekiga 3.0.2 on Fedora 10 x86_64 (64 bit). I have a VoIP > > account with my internet provider and I have setup Ekiga to use that > > and that all works fine. However, within a couple of minutes, the > > incoming calls do not work anymore. It goes straight to the voice > > mail. If I de-register and register again, all works again for a > > minute or 2 and then same problem. Outgoing calls are fine and stable. > > > > What can be a possible cause and/or what can I do to further > > investigate. To eliminate the fact that it is not a > > router/infrastructure etc issue, I have tested with Twinkle. This > > package seems stable both incoming as outgoing. So the issue appears > > to be with Ekiga. > > > > How can I see how I am registered in Ekiga? I want to see something > > like this: ;q=0.500;expires=360. As > > outgoing calls still work, registration must perhaps get confused > > somehow and change to something like: > > ;q=0.500;expires=360 (I am only > > guessing) meaning that I am still connected to a sip server, but not > > linked anymore to the incoming number. > > > > Any ideas/tips/hints/solutions are appreciated. > > Perhaps the NAT binding on the router is closed. > > We send a 'probe' every 10 seconds to keep it alive. > > Perhaps you could try sending a probe every 3 seconds. To change this, > you can edit the following key : > /apps/ekiga/protocols/sip/binding_timeout > using gconftool or gconf-editor. > > Do not edit the config files manually, it won't work. Thanks Damien. Tried that, but it did not work unfortunately. Fedora release ekiga-3.0.2-2.fc10 update yesterday. Updated and also no change. Is it possible that the problem is on the provider site? If so, which value/setting should I ask them to set/use? Anything else in Ekiga I can set. Proxy for instance? Can I edit STUN settings in Ekiga? Any other ideas? Thanks again. Bas. -------------- next part -------------- An HTML attachment was scrubbed... URL: From bas.driessen at xobas.com Sat Feb 14 14:00:39 2009 From: bas.driessen at xobas.com (Bas Driessen) Date: Sun, 15 Feb 2009 00:00:39 +1000 Subject: [Ekiga-list] Problems incoming calls. In-Reply-To: <1234616786.3912.2.camel@ams.xobas.net> References: <1234572499.4794.11.camel@ams.xobas.net> <1234607920.4280.2.camel@scorpion.multitel.be> <1234616786.3912.2.camel@ams.xobas.net> Message-ID: <1234620039.3912.6.camel@ams.xobas.net> On Sat, 2009-02-14 at 23:06 +1000, Bas Driessen wrote: > On Sat, 2009-02-14 at 11:38 +0100, Damien Sandras wrote: > > > Le samedi 14 f?vrier 2009 ? 10:48 +1000, Bas Driessen a ?crit : > > > Hello, > > > > > > I am using Ekiga 3.0.2 on Fedora 10 x86_64 (64 bit). I have a VoIP > > > account with my internet provider and I have setup Ekiga to use that > > > and that all works fine. However, within a couple of minutes, the > > > incoming calls do not work anymore. It goes straight to the voice > > > mail. If I de-register and register again, all works again for a > > > minute or 2 and then same problem. Outgoing calls are fine and stable. > > > > > > What can be a possible cause and/or what can I do to further > > > investigate. To eliminate the fact that it is not a > > > router/infrastructure etc issue, I have tested with Twinkle. This > > > package seems stable both incoming as outgoing. So the issue appears > > > to be with Ekiga. > > > > > > How can I see how I am registered in Ekiga? I want to see something > > > like this: ;q=0.500;expires=360. As > > > outgoing calls still work, registration must perhaps get confused > > > somehow and change to something like: > > > ;q=0.500;expires=360 (I am only > > > guessing) meaning that I am still connected to a sip server, but not > > > linked anymore to the incoming number. > > > > > > Any ideas/tips/hints/solutions are appreciated. > > > > Perhaps the NAT binding on the router is closed. > > > > We send a 'probe' every 10 seconds to keep it alive. > > > > Perhaps you could try sending a probe every 3 seconds. To change this, > > you can edit the following key : > > /apps/ekiga/protocols/sip/binding_timeout > > using gconftool or gconf-editor. > > > > Do not edit the config files manually, it won't work. > > > Thanks Damien. Tried that, but it did not work unfortunately. Fedora > release ekiga-3.0.2-2.fc10 update yesterday. Updated and also no > change. > > Is it possible that the problem is on the provider site? If so, which > value/setting should I ask them to set/use? > > Anything else in Ekiga I can set. Proxy for instance? Can I edit STUN > settings in Ekiga? Any other ideas? > > Thanks again. > Can the following be an issue? It looks to me it is retrying something 3 times and then give up? (note, I have changed my real SIP number for a dummy number for obvious privacy reasons) 2009/02/14 23:57:15.447 10:59.032 Housekeeper:0x3ef66950 SIP Starting PUBLISH for offline retry 2009/02/14 23:57:15.447 10:59.032 Housekeeper:0x3ef66950 SIP Expiry time for PUBLISH set to 500 seconds. 2009/02/14 23:57:15.515 10:59.100 Housekeeper:0x3ef66950 SIP Transaction remote address is udp$203.2.134.1:5060 2009/02/14 23:57:15.515 10:59.100 Housekeeper:0x3ef66950 SIP Sending PDU PUBLISH sip:012345678 at sip.internode.on.net (881 bytes) to: rem=udp $203.2.134.1:5060,local=udp$59.167.214.42:5060,if=192.168.1.14%br0 2009/02/14 23:57:15.516 10:59.101 Housekeeper:0x3ef66950 SIP Expiry time for PUBLISH set to 500 seconds. 2009/02/14 23:57:15.553 10:59.138 Housekeeper:0x3ef66950 SIP Transaction remote address is udp$203.2.134.1:5060 2009/02/14 23:57:15.553 10:59.138 Housekeeper:0x3ef66950 SIP Sending PDU PUBLISH sip:012345678 at sip.internode.on.net (881 bytes) to: rem=udp $203.2.134.1:5060,local=udp$192.168.122.1:5060,if=192.168.122.1%virbr0 2009/02/14 23:57:15.592 10:59.177 Opal Liste...0x3ef25950 OpalUDP Binding to interface: 59.167.214.42:5060 2009/02/14 23:57:15.592 10:59.177 Opal Liste...0x3ef25950 SIP No Content-Length present from udp$203.2.134.1:5060, reading till end of datagram/stream. 2009/02/14 23:57:15.592 10:59.177 Opal Liste...0x3ef25950 SIP PDU 405 Method Not Allowed received: rem=udp$203.2.134.1:5060,local=udp $59.167.214.42:5060,if=192.168.1.14%br0 2009/02/14 23:57:15.593 10:59.178 Opal Liste...0x3ef25950 SIP Transaction 39 PUBLISH completed. 2009/02/14 23:57:15.593 10:59.178 Opal Liste...0x3ef25950 Opal Transport clean up on termination 2009/02/14 23:57:15.947 10:59.532 Housekeeper:0x3ef66950 SIP Transaction 40 PUBLISH timeout, making retry 1 2009/02/14 23:57:15.948 10:59.533 Housekeeper:0x3ef66950 SIP Sending PDU PUBLISH sip:012345678 at sip.internode.on.net (881 bytes) to: rem=udp $203.2.134.1:5060,local=udp$192.168.122.1:5060,if=192.168.122.1%virbr0 2009/02/14 23:57:16.594 11:00.179 Housekeeper:0x3ef66950 SIP Set state Terminated_Success for transaction 39 PUBLISH 2009/02/14 23:57:16.947 11:00.532 Housekeeper:0x3ef66950 SIP Transaction 40 PUBLISH timeout, making retry 2 2009/02/14 23:57:16.948 11:00.533 Housekeeper:0x3ef66950 SIP Sending PDU PUBLISH sip:012345678 at sip.internode.on.net (881 bytes) to: rem=udp $203.2.134.1:5060,local=udp$192.168.122.1:5060,if=192.168.122.1%virbr0 2009/02/14 23:57:18.948 11:02.533 Housekeeper:0x3ef66950 SIP Transaction 40 PUBLISH timeout, making retry 3 2009/02/14 23:57:18.948 11:02.533 Housekeeper:0x3ef66950 SIP Sending PDU PUBLISH sip:012345678 at sip.internode.on.net (881 bytes) to: rem=udp $203.2.134.1:5060,local=udp$192.168.122.1:5060,if=192.168.122.1%virbr0 2009/02/14 23:57:21.447 11:05.032 Housekeeper:0x3ef66950 SIP Set state Terminated_Timeout for transaction 40 PUBLISH Thanks, Bas. -------------- next part -------------- An HTML attachment was scrubbed... URL: From dsandras at seconix.com Sat Feb 14 14:02:13 2009 From: dsandras at seconix.com (Damien Sandras) Date: Sat, 14 Feb 2009 15:02:13 +0100 Subject: [Ekiga-list] Problems incoming calls. In-Reply-To: <1234617978.3912.3.camel@ams.xobas.net> References: <1234572499.4794.11.camel@ams.xobas.net> <1234607920.4280.2.camel@scorpion.multitel.be> <1234617978.3912.3.camel@ams.xobas.net> Message-ID: <1234620133.4280.12.camel@scorpion.multitel.be> Le samedi 14 f?vrier 2009 ? 23:26 +1000, Bas Driessen a ?crit : > > > > Perhaps the NAT binding on the router is closed. > > > > We send a 'probe' every 10 seconds to keep it alive. > > > > Perhaps you could try sending a probe every 3 seconds. To change this, > > you can edit the following key : > > /apps/ekiga/protocols/sip/binding_timeout > > using gconftool or gconf-editor. > > > > Do not edit the config files manually, it won't work. > > Thanks Damien. Tried that, but it did not work unfortunately. Fedora > release ekiga-3.0.2-2.fc10 update yesterday. Updated and also no > change. > > Is it possible that the problem is on the provider site? If so, which > value/setting should I ask them to set/use? > > Anything else in Ekiga I can set. Proxy for instance? Can I edit STUN > settings in Ekiga? Any other ideas? I think you should ask them. What you could do also is reconfigure Ekiga so that the registration timeout is set to 120 (2 minutes). That way, it will register every 2 minutes with your provider. It will hide the 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 bas.driessen at xobas.com Sat Feb 14 14:07:35 2009 From: bas.driessen at xobas.com (Bas Driessen) Date: Sun, 15 Feb 2009 00:07:35 +1000 Subject: [Ekiga-list] Problems incoming calls. In-Reply-To: <1234620133.4280.12.camel@scorpion.multitel.be> References: <1234572499.4794.11.camel@ams.xobas.net> <1234607920.4280.2.camel@scorpion.multitel.be> <1234617978.3912.3.camel@ams.xobas.net> <1234620133.4280.12.camel@scorpion.multitel.be> Message-ID: <1234620455.3912.7.camel@ams.xobas.net> On Sat, 2009-02-14 at 15:02 +0100, Damien Sandras wrote: > Le samedi 14 f?vrier 2009 ? 23:26 +1000, Bas Driessen a ?crit : > > > > > > Perhaps the NAT binding on the router is closed. > > > > > > We send a 'probe' every 10 seconds to keep it alive. > > > > > > Perhaps you could try sending a probe every 3 seconds. To change this, > > > you can edit the following key : > > > /apps/ekiga/protocols/sip/binding_timeout > > > using gconftool or gconf-editor. > > > > > > Do not edit the config files manually, it won't work. > > > > Thanks Damien. Tried that, but it did not work unfortunately. Fedora > > release ekiga-3.0.2-2.fc10 update yesterday. Updated and also no > > change. > > > > Is it possible that the problem is on the provider site? If so, which > > value/setting should I ask them to set/use? > > > > Anything else in Ekiga I can set. Proxy for instance? Can I edit STUN > > settings in Ekiga? Any other ideas? > > I think you should ask them. What you could do also is reconfigure Ekiga > so that the registration timeout is set to 120 (2 minutes). That way, it > will register every 2 minutes with your provider. It will hide the > problem. I just tried before setting it to 30 seconds. Same problem. (The default is 60 btw, which is still faster than the 120 you suggest). Thanks, Bas. -------------- next part -------------- An HTML attachment was scrubbed... URL: From dsandras at seconix.com Sat Feb 14 14:17:25 2009 From: dsandras at seconix.com (Damien Sandras) Date: Sat, 14 Feb 2009 15:17:25 +0100 Subject: [Ekiga-list] Problems incoming calls. In-Reply-To: <1234620455.3912.7.camel@ams.xobas.net> References: <1234572499.4794.11.camel@ams.xobas.net> <1234607920.4280.2.camel@scorpion.multitel.be> <1234617978.3912.3.camel@ams.xobas.net> <1234620133.4280.12.camel@scorpion.multitel.be> <1234620455.3912.7.camel@ams.xobas.net> Message-ID: <1234621045.4280.14.camel@scorpion.multitel.be> Le dimanche 15 f?vrier 2009 ? 00:07 +1000, Bas Driessen a ?crit : > On Sat, 2009-02-14 at 15:02 +0100, Damien Sandras wrote: > > Le samedi 14 f?vrier 2009 ? 23:26 +1000, Bas Driessen a ?crit : > > > > > > > > Perhaps the NAT binding on the router is closed. > > > > > > > > We send a 'probe' every 10 seconds to keep it alive. > > > > > > > > Perhaps you could try sending a probe every 3 seconds. To change this, > > > > you can edit the following key : > > > > /apps/ekiga/protocols/sip/binding_timeout > > > > using gconftool or gconf-editor. > > > > > > > > Do not edit the config files manually, it won't work. > > > > > > Thanks Damien. Tried that, but it did not work unfortunately. Fedora > > > release ekiga-3.0.2-2.fc10 update yesterday. Updated and also no > > > change. > > > > > > Is it possible that the problem is on the provider site? If so, which > > > value/setting should I ask them to set/use? > > > > > > Anything else in Ekiga I can set. Proxy for instance? Can I edit STUN > > > settings in Ekiga? Any other ideas? > > > > I think you should ask them. What you could do also is reconfigure Ekiga > > so that the registration timeout is set to 120 (2 minutes). That way, it > > will register every 2 minutes with your provider. It will hide the > > problem. > > I just tried before setting it to 30 seconds. Same problem. (The > default is 60 btw, which is still faster than the 120 you suggest). In that case, and if you are sure your modem is not the culprit, I really suggest you to report a bug to your sip provider. -- _ 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 bas.driessen at xobas.com Sat Feb 14 14:38:59 2009 From: bas.driessen at xobas.com (Bas Driessen) Date: Sun, 15 Feb 2009 00:38:59 +1000 Subject: [Ekiga-list] Problems incoming calls. In-Reply-To: <1234621045.4280.14.camel@scorpion.multitel.be> References: <1234572499.4794.11.camel@ams.xobas.net> <1234607920.4280.2.camel@scorpion.multitel.be> <1234617978.3912.3.camel@ams.xobas.net> <1234620133.4280.12.camel@scorpion.multitel.be> <1234620455.3912.7.camel@ams.xobas.net> <1234621045.4280.14.camel@scorpion.multitel.be> Message-ID: <1234622339.3912.13.camel@ams.xobas.net> On Sat, 2009-02-14 at 15:17 +0100, Damien Sandras wrote: > Le dimanche 15 f?vrier 2009 ? 00:07 +1000, Bas Driessen a ?crit : > > On Sat, 2009-02-14 at 15:02 +0100, Damien Sandras wrote: > > > Le samedi 14 f?vrier 2009 ? 23:26 +1000, Bas Driessen a ?crit : > > > > > > > > > > Perhaps the NAT binding on the router is closed. > > > > > > > > > > We send a 'probe' every 10 seconds to keep it alive. > > > > > > > > > > Perhaps you could try sending a probe every 3 seconds. To change this, > > > > > you can edit the following key : > > > > > /apps/ekiga/protocols/sip/binding_timeout > > > > > using gconftool or gconf-editor. > > > > > > > > > > Do not edit the config files manually, it won't work. > > > > > > > > Thanks Damien. Tried that, but it did not work unfortunately. Fedora > > > > release ekiga-3.0.2-2.fc10 update yesterday. Updated and also no > > > > change. > > > > > > > > Is it possible that the problem is on the provider site? If so, which > > > > value/setting should I ask them to set/use? > > > > > > > > Anything else in Ekiga I can set. Proxy for instance? Can I edit STUN > > > > settings in Ekiga? Any other ideas? > > > > > > I think you should ask them. What you could do also is reconfigure Ekiga > > > so that the registration timeout is set to 120 (2 minutes). That way, it > > > will register every 2 minutes with your provider. It will hide the > > > problem. > > > > I just tried before setting it to 30 seconds. Same problem. (The > > default is 60 btw, which is still faster than the 120 you suggest). > > In that case, and if you are sure your modem is not the culprit, I > really suggest you to report a bug to your sip provider. Thanks for your help Damien. As mentioned before, Twinkle (SIP client) works OK and is stable with the same VoIP account on the same machine here. That is what makes me believe that this is an Ekiga issue. Have tried it from my Fedora laptop as well. Same results. Too bad ... Ekiga is so much better than the other VoIP clients, so that is why I am really desperate to get it to work. Will continue testing, googling etc. Again thanks for your help today and will report back once I find the cause. Bas. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ekiga at 0x1b.com Sat Feb 14 16:08:29 2009 From: Ekiga at 0x1b.com (Ed) Date: Sat, 14 Feb 2009 09:08:29 -0700 Subject: [Ekiga-list] Fedora Core 10 - Ekiga 3.0.2 registration timeout() In-Reply-To: <49961686.3060802@cchtml.com> References: <7c8767520902091902j7ad74d9du4ee4626799ab7970@mail.gmail.com> <7c8767520902091909r25e4a0d8p8da2f4d5db9ecbdf@mail.gmail.com> <7c8767520902101827w18092b71md419e1da9479c2f9@mail.gmail.com> <200902132146.22555.wolfram.wagner@web.de> <6e30f6790902131515x50430d73ne33dc998687fe8f1@mail.gmail.com> <49961686.3060802@cchtml.com> Message-ID: <6e30f6790902140808va660360t8ad8bec8d7ff44ec@mail.gmail.com> On Fri, Feb 13, 2009 at 5:55 PM, Michael Cronenworth wrote: > Ed wrote: > > Fedora 10 got all enthusiastic with SELinux maybe? > You might toggle SELinux in & out of permissive mode while you're in > flipin'-switches mode. > man setenforce & sestatus > ymmv > > > I'm using Ekiga 3.0.2 and Fedora 10 with SELinux in Enforced mode. I have no > issues. > > In fact, I haven't had a single SELinux related issue since Fedora 9. I've > been in enforced mode for almost a year now. If you do run into a problem > there is a graphical tool that notifies you of SELinux denials and offers > suggestions on workarounds. You can drop the SELinux jokes. I for one would love to hear some good SELinux jokes* ;) And i wouldn't suggest running without it - new tools etc make it very useful - especially with the new guide on the Fedora site. http://docs.fedoraproject.org/selinux-user-guide/ but in terms of "big & easy" diagnostic checks, aka flipin'-switches mode, it is up there with the firewall & rebooting. well maybe you can hold off on rebooting for a bit... And, like your local firewall, I wouldn't recommend running a system for very long without it Bas. (once you've got Ekiga working) sorry I couldn't help. *we have a LUG here and any new material is greatly appreciated From dsandras at seconix.com Sat Feb 14 17:37:27 2009 From: dsandras at seconix.com (Damien Sandras) Date: Sat, 14 Feb 2009 18:37:27 +0100 Subject: [Ekiga-list] Problems incoming calls. In-Reply-To: <1234622339.3912.13.camel@ams.xobas.net> References: <1234572499.4794.11.camel@ams.xobas.net> <1234607920.4280.2.camel@scorpion.multitel.be> <1234617978.3912.3.camel@ams.xobas.net> <1234620133.4280.12.camel@scorpion.multitel.be> <1234620455.3912.7.camel@ams.xobas.net> <1234621045.4280.14.camel@scorpion.multitel.be> <1234622339.3912.13.camel@ams.xobas.net> Message-ID: <1234633047.4280.16.camel@scorpion.multitel.be> Le dimanche 15 f?vrier 2009 ? 00:38 +1000, Bas Driessen a ?crit : > On Sat, 2009-02-14 at 15:17 +0100, Damien Sandras wrote: > > Le dimanche 15 f?vrier 2009 ? 00:07 +1000, Bas Driessen a ?crit : > > > On Sat, 2009-02-14 at 15:02 +0100, Damien Sandras wrote: > > > > Le samedi 14 f?vrier 2009 ? 23:26 +1000, Bas Driessen a ?crit : > > > > > > > > > > > > Perhaps the NAT binding on the router is closed. > > > > > > > > > > > > We send a 'probe' every 10 seconds to keep it alive. > > > > > > > > > > > > Perhaps you could try sending a probe every 3 seconds. To change this, > > > > > > you can edit the following key : > > > > > > /apps/ekiga/protocols/sip/binding_timeout > > > > > > using gconftool or gconf-editor. > > > > > > > > > > > > Do not edit the config files manually, it won't work. > > > > > > > > > > Thanks Damien. Tried that, but it did not work unfortunately. Fedora > > > > > release ekiga-3.0.2-2.fc10 update yesterday. Updated and also no > > > > > change. > > > > > > > > > > Is it possible that the problem is on the provider site? If so, which > > > > > value/setting should I ask them to set/use? > > > > > > > > > > Anything else in Ekiga I can set. Proxy for instance? Can I edit STUN > > > > > settings in Ekiga? Any other ideas? > > > > > > > > I think you should ask them. What you could do also is reconfigure Ekiga > > > > so that the registration timeout is set to 120 (2 minutes). That way, it > > > > will register every 2 minutes with your provider. It will hide the > > > > problem. > > > > > > I just tried before setting it to 30 seconds. Same problem. (The > > > default is 60 btw, which is still faster than the 120 you suggest). > > > > In that case, and if you are sure your modem is not the culprit, I > > really suggest you to report a bug to your sip provider. > > Thanks for your help Damien. As mentioned before, Twinkle (SIP client) > works OK and is stable with the same VoIP account on the same machine > here. That is what makes me believe that this is an Ekiga issue. Have > tried it from my Fedora laptop as well. Same results. Too bad ... > Ekiga is so much better than the other VoIP clients, so that is why I > am really desperate to get it to work. Are you using STUN in both cases? -- _ 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 mariofutire at googlemail.com Sat Feb 14 19:31:30 2009 From: mariofutire at googlemail.com (Andrea) Date: Sat, 14 Feb 2009 19:31:30 +0000 Subject: [Ekiga-list] Feature request: stop screensaver Message-ID: Hi, I would like to know whether other people would be interested in adding a config flag to stop the screensaver during a video call. I wanted to try to add id myself I and I found that there is a call to reset the counter XResetScreensaver. I would like to ask the developers if there is an easy point in the code that is called often during a call. I would add later the relevant config option. Thanks Andrea From bas.driessen at xobas.com Sun Feb 15 00:01:44 2009 From: bas.driessen at xobas.com (Bas Driessen) Date: Sun, 15 Feb 2009 10:01:44 +1000 Subject: [Ekiga-list] Problems incoming calls. In-Reply-To: <1234633047.4280.16.camel@scorpion.multitel.be> References: <1234572499.4794.11.camel@ams.xobas.net> <1234607920.4280.2.camel@scorpion.multitel.be> <1234617978.3912.3.camel@ams.xobas.net> <1234620133.4280.12.camel@scorpion.multitel.be> <1234620455.3912.7.camel@ams.xobas.net> <1234621045.4280.14.camel@scorpion.multitel.be> <1234622339.3912.13.camel@ams.xobas.net> <1234633047.4280.16.camel@scorpion.multitel.be> Message-ID: <1234656104.782.9.camel@ams.xobas.net> On Sat, 2009-02-14 at 18:37 +0100, Damien Sandras wrote: > Le dimanche 15 f?vrier 2009 ? 00:38 +1000, Bas Driessen a ?crit : > > On Sat, 2009-02-14 at 15:17 +0100, Damien Sandras wrote: > > > Le dimanche 15 f?vrier 2009 ? 00:07 +1000, Bas Driessen a ?crit : > > > > On Sat, 2009-02-14 at 15:02 +0100, Damien Sandras wrote: > > > > > Le samedi 14 f?vrier 2009 ? 23:26 +1000, Bas Driessen a ?crit : > > > > > > > > > > > > > > Perhaps the NAT binding on the router is closed. > > > > > > > > > > > > > > We send a 'probe' every 10 seconds to keep it alive. > > > > > > > > > > > > > > Perhaps you could try sending a probe every 3 seconds. To change this, > > > > > > > you can edit the following key : > > > > > > > /apps/ekiga/protocols/sip/binding_timeout > > > > > > > using gconftool or gconf-editor. > > > > > > > > > > > > > > Do not edit the config files manually, it won't work. > > > > > > > > > > > > Thanks Damien. Tried that, but it did not work unfortunately. Fedora > > > > > > release ekiga-3.0.2-2.fc10 update yesterday. Updated and also no > > > > > > change. > > > > > > > > > > > > Is it possible that the problem is on the provider site? If so, which > > > > > > value/setting should I ask them to set/use? > > > > > > > > > > > > Anything else in Ekiga I can set. Proxy for instance? Can I edit STUN > > > > > > settings in Ekiga? Any other ideas? > > > > > > > > > > I think you should ask them. What you could do also is reconfigure Ekiga > > > > > so that the registration timeout is set to 120 (2 minutes). That way, it > > > > > will register every 2 minutes with your provider. It will hide the > > > > > problem. > > > > > > > > I just tried before setting it to 30 seconds. Same problem. (The > > > > default is 60 btw, which is still faster than the 120 you suggest). > > > > > > In that case, and if you are sure your modem is not the culprit, I > > > really suggest you to report a bug to your sip provider. > > > > Thanks for your help Damien. As mentioned before, Twinkle (SIP client) > > works OK and is stable with the same VoIP account on the same machine > > here. That is what makes me believe that this is an Ekiga issue. Have > > tried it from my Fedora laptop as well. Same results. Too bad ... > > Ekiga is so much better than the other VoIP clients, so that is why I > > am really desperate to get it to work. > > Are you using STUN in both cases? Not sure how to set that in Ekiga. In older versions it was an option in the GUI somewhere. The only STUN reference I can see now is in gconf (/apps/ekiga/general/nat/stun_server) I left this at the default which is stun.ekiga.net. Do I leave that setting like that even though I am going through a different VoIP provider? Also what I want to find out today is if the issue has anything to do with the Fedora 10 64 bit build. I have had several 64 bit issues with other packages in the past on Fedora. I see that there is also a Windows version of Ekiga. I am going to install that on a Windows box here just to find out if it is a platform/distribution related issue. What I did find out since last posting is that the issue is not related to re-registering. Once incoming calls do not work anymore, even if I manually go to accounts de-register, register, incoming calls still do not work. I have to completely shutdown Ekiga and start it up again for it to work. Will post back results. Bas. -------------- next part -------------- An HTML attachment was scrubbed... URL: From dsandras at seconix.com Sun Feb 15 12:10:40 2009 From: dsandras at seconix.com (Damien Sandras) Date: Sun, 15 Feb 2009 13:10:40 +0100 Subject: [Ekiga-list] Problems incoming calls. In-Reply-To: <1234656104.782.9.camel@ams.xobas.net> References: <1234572499.4794.11.camel@ams.xobas.net> <1234607920.4280.2.camel@scorpion.multitel.be> <1234617978.3912.3.camel@ams.xobas.net> <1234620133.4280.12.camel@scorpion.multitel.be> <1234620455.3912.7.camel@ams.xobas.net> <1234621045.4280.14.camel@scorpion.multitel.be> <1234622339.3912.13.camel@ams.xobas.net> <1234633047.4280.16.camel@scorpion.multitel.be> <1234656104.782.9.camel@ams.xobas.net> Message-ID: <1234699840.4287.1.camel@scorpion.multitel.be> Le dimanche 15 f?vrier 2009 ? 10:01 +1000, Bas Driessen a ?crit : > > Are you using STUN in both cases? > > Not sure how to set that in Ekiga. In older versions it was an option > in the GUI somewhere. The only STUN reference I can see now is in > gconf (/apps/ekiga/general/nat/stun_server) I left this at the default > which is stun.ekiga.net. Do I leave that setting like that even though > I am going through a different VoIP provider? > > Also what I want to find out today is if the issue has anything to do > with the Fedora 10 64 bit build. I have had several 64 bit issues with > other packages in the past on Fedora. I see that there is also a > Windows version of Ekiga. I am going to install that on a Windows box > here just to find out if it is a platform/distribution related issue. > > What I did find out since last posting is that the issue is not > related to re-registering. Once incoming calls do not work anymore, > even if I manually go to accounts de-register, register, incoming > calls still do not work. I have to completely shutdown Ekiga and start > it up again for it to work. > > Will post back results. > What about twinkle, are you using STUN with twinkle or not ? Also, could you post a -d 4 output to pastebin with a call attempt ? -- _ 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 bas.driessen at xobas.com Sun Feb 15 12:26:30 2009 From: bas.driessen at xobas.com (Bas Driessen) Date: Sun, 15 Feb 2009 22:26:30 +1000 Subject: [Ekiga-list] Problems incoming calls. In-Reply-To: <1234699840.4287.1.camel@scorpion.multitel.be> References: <1234572499.4794.11.camel@ams.xobas.net> <1234607920.4280.2.camel@scorpion.multitel.be> <1234617978.3912.3.camel@ams.xobas.net> <1234620133.4280.12.camel@scorpion.multitel.be> <1234620455.3912.7.camel@ams.xobas.net> <1234621045.4280.14.camel@scorpion.multitel.be> <1234622339.3912.13.camel@ams.xobas.net> <1234633047.4280.16.camel@scorpion.multitel.be> <1234656104.782.9.camel@ams.xobas.net> <1234699840.4287.1.camel@scorpion.multitel.be> Message-ID: <1234700790.3741.8.camel@ams.xobas.net> On Sun, 2009-02-15 at 13:10 +0100, Damien Sandras wrote: > Le dimanche 15 f?vrier 2009 ? 10:01 +1000, Bas Driessen a ?crit : > > > > Are you using STUN in both cases? > > > > Not sure how to set that in Ekiga. In older versions it was an option > > in the GUI somewhere. The only STUN reference I can see now is in > > gconf (/apps/ekiga/general/nat/stun_server) I left this at the default > > which is stun.ekiga.net. Do I leave that setting like that even though > > I am going through a different VoIP provider? > > > > Also what I want to find out today is if the issue has anything to do > > with the Fedora 10 64 bit build. I have had several 64 bit issues with > > other packages in the past on Fedora. I see that there is also a > > Windows version of Ekiga. I am going to install that on a Windows box > > here just to find out if it is a platform/distribution related issue. > > > > What I did find out since last posting is that the issue is not > > related to re-registering. Once incoming calls do not work anymore, > > even if I manually go to accounts de-register, register, incoming > > calls still do not work. I have to completely shutdown Ekiga and start > > it up again for it to work. > > > > Will post back results. > > > > What about twinkle, are you using STUN with twinkle or not ? > > Also, could you post a -d 4 output to pastebin with a call attempt ? OK, I believe I am starting to understand what is happening. My Router (Netgear DGN2000) has the feature SIP ALG enabled. If I disable that, then primarily testing shows that Ekiga is stable with incoming calls. The reason that twinkle works with SIP ALG enabled is that there is an option selected called "NAT traversal not needed" which has been selected. To be complete, Twinkle has 3 options: -1 NAT Traversal not needed -2 Use statically configured public IP address. (and an ip address can be entered) -3 Use STUN. (and a STUN server can be entered) OK, so now I have enabled this SIP ALG and disabled STUN with Ekiga, but no incoming calls now. The way I disabled STUN is to remove the value in key /apps/ekiga/general/nat/stun_server (make it blank). Is that the correct way? I would prefer to run Ekiga without STUN. Any additional I can set to disable the NAT traversal in Ekiga? Btw, my testing on Windows and Fedora 10 64 bit have the same results, which is good! Thanks, Bas. -------------- next part -------------- An HTML attachment was scrubbed... URL: From bas.driessen at xobas.com Sun Feb 15 12:38:05 2009 From: bas.driessen at xobas.com (Bas Driessen) Date: Sun, 15 Feb 2009 22:38:05 +1000 Subject: [Ekiga-list] Problems incoming calls. In-Reply-To: <1234700790.3741.8.camel@ams.xobas.net> References: <1234572499.4794.11.camel@ams.xobas.net> <1234607920.4280.2.camel@scorpion.multitel.be> <1234617978.3912.3.camel@ams.xobas.net> <1234620133.4280.12.camel@scorpion.multitel.be> <1234620455.3912.7.camel@ams.xobas.net> <1234621045.4280.14.camel@scorpion.multitel.be> <1234622339.3912.13.camel@ams.xobas.net> <1234633047.4280.16.camel@scorpion.multitel.be> <1234656104.782.9.camel@ams.xobas.net> <1234699840.4287.1.camel@scorpion.multitel.be> <1234700790.3741.8.camel@ams.xobas.net> Message-ID: <1234701485.3741.10.camel@ams.xobas.net> On Sun, 2009-02-15 at 22:26 +1000, Bas Driessen wrote: > On Sun, 2009-02-15 at 13:10 +0100, Damien Sandras wrote: > > > Le dimanche 15 f?vrier 2009 ? 10:01 +1000, Bas Driessen a ?crit : > > > > > > Are you using STUN in both cases? > > > > > > Not sure how to set that in Ekiga. In older versions it was an option > > > in the GUI somewhere. The only STUN reference I can see now is in > > > gconf (/apps/ekiga/general/nat/stun_server) I left this at the default > > > which is stun.ekiga.net. Do I leave that setting like that even though > > > I am going through a different VoIP provider? > > > > > > Also what I want to find out today is if the issue has anything to do > > > with the Fedora 10 64 bit build. I have had several 64 bit issues with > > > other packages in the past on Fedora. I see that there is also a > > > Windows version of Ekiga. I am going to install that on a Windows box > > > here just to find out if it is a platform/distribution related issue. > > > > > > What I did find out since last posting is that the issue is not > > > related to re-registering. Once incoming calls do not work anymore, > > > even if I manually go to accounts de-register, register, incoming > > > calls still do not work. I have to completely shutdown Ekiga and start > > > it up again for it to work. > > > > > > Will post back results. > > > > > > > What about twinkle, are you using STUN with twinkle or not ? > > > > Also, could you post a -d 4 output to pastebin with a call attempt ? > > > > OK, I believe I am starting to understand what is happening. My Router > (Netgear DGN2000) has the feature SIP ALG enabled. If I disable that, > then primarily testing shows that Ekiga is stable with incoming calls. > The reason that twinkle works with SIP ALG enabled is that there is an > option selected called "NAT traversal not needed" which has been > selected. To be complete, Twinkle has 3 options: > > -1 NAT Traversal not needed > -2 Use statically configured public IP address. (and an ip address can > be entered) > -3 Use STUN. (and a STUN server can be entered) > > OK, so now I have enabled this SIP ALG and disabled STUN with Ekiga, > but no incoming calls now. > > The way I disabled STUN is to remove the value in > key /apps/ekiga/general/nat/stun_server (make it blank). Is that the > correct way? > > I would prefer to run Ekiga without STUN. Any additional I can set to > disable the NAT traversal in Ekiga? > > Btw, my testing on Windows and Fedora 10 64 bit have the same results, > which is good! > OK, I have set SIP ALG to enabled, rebooted the router and removed the STUN value. I am getting incoming calls now with Ekiga. Now testing if it is stable. -------------- next part -------------- An HTML attachment was scrubbed... URL: From blino at mandriva.org Sun Feb 15 13:14:18 2009 From: blino at mandriva.org (Olivier Blin) Date: Sun, 15 Feb 2009 14:14:18 +0100 Subject: [Ekiga-list] ekiga 3 and 16bpp displays In-Reply-To: <1234608102.4280.4.camel@scorpion.multitel.be> (Damien Sandras's message of "Sat\, 14 Feb 2009 11\:41\:42 +0100") References: <1234608102.4280.4.camel@scorpion.multitel.be> Message-ID: Damien Sandras writes: > Le vendredi 13 f?vrier 2009 ? 18:35 +0100, Olivier Blin a ?crit : >> Hello, >> >> I have a crash with ekiga (3.0.x or 3.1.x) when using a 16bpp display. >> Here is an interesting pointer in the trace: >> Could not find visual with colordepth of 24 bits per pixel >> >> It seems that XWindow::checkDepth() fallbacks to 24bpp, but it does not >> support 16bpp. >> >> The log + trace can be found here: >> http://people.mandriva.com/~blino/ekiga-crash-16bpp.log >> >> Is ekiga supposed to work with only 24bpp and 32bpp displays? > > I think so yes. > >> What can be done to make it work on 16bpp displays? > > Fix the code so that it works with 16bpp too :-) Ok, so it mostly needs to be implemented in ptlib? That would mean: - in ptlib, src/ptlib/common/vconvert.cxx: o add support for RGB565 in PStandardColourConverter::YUV420PtoRGB() o add wrappers for this RGB565 mode - in ekiga, lib/gui/xwindow.cpp: o add a new xFormats entry: {"RGB16", 16, 2, LSBFirst, 0x0000F800, 0x000007E0, 0x0000001F}, o fallback to 16bpp in XWindow::checkDepth() when appropriate Does it sound sensible? > But is 16bpp that common ? Maybe not on most modern x86 hardware, but for example on our MIPS platform for the Gdium project, we prefer to use 16bpp for memory and bandwith/speed reasons. Thanks -- Olivier Blin (blino) - Mandriva From bas.driessen at xobas.com Sun Feb 15 13:41:29 2009 From: bas.driessen at xobas.com (Bas Driessen) Date: Sun, 15 Feb 2009 23:41:29 +1000 Subject: [Ekiga-list] Problems incoming calls. In-Reply-To: <1234701485.3741.10.camel@ams.xobas.net> References: <1234572499.4794.11.camel@ams.xobas.net> <1234607920.4280.2.camel@scorpion.multitel.be> <1234617978.3912.3.camel@ams.xobas.net> <1234620133.4280.12.camel@scorpion.multitel.be> <1234620455.3912.7.camel@ams.xobas.net> <1234621045.4280.14.camel@scorpion.multitel.be> <1234622339.3912.13.camel@ams.xobas.net> <1234633047.4280.16.camel@scorpion.multitel.be> <1234656104.782.9.camel@ams.xobas.net> <1234699840.4287.1.camel@scorpion.multitel.be> <1234700790.3741.8.camel@ams.xobas.net> <1234701485.3741.10.camel@ams.xobas.net> Message-ID: <1234705289.3741.13.camel@ams.xobas.net> On Sun, 2009-02-15 at 22:38 +1000, Bas Driessen wrote: > On Sun, 2009-02-15 at 22:26 +1000, Bas Driessen wrote: > > > On Sun, 2009-02-15 at 13:10 +0100, Damien Sandras wrote: > > > > > Le dimanche 15 f?vrier 2009 ? 10:01 +1000, Bas Driessen a ?crit : > > > > > > > > Are you using STUN in both cases? > > > > > > > > Not sure how to set that in Ekiga. In older versions it was an option > > > > in the GUI somewhere. The only STUN reference I can see now is in > > > > gconf (/apps/ekiga/general/nat/stun_server) I left this at the default > > > > which is stun.ekiga.net. Do I leave that setting like that even though > > > > I am going through a different VoIP provider? > > > > > > > > Also what I want to find out today is if the issue has anything to do > > > > with the Fedora 10 64 bit build. I have had several 64 bit issues with > > > > other packages in the past on Fedora. I see that there is also a > > > > Windows version of Ekiga. I am going to install that on a Windows box > > > > here just to find out if it is a platform/distribution related issue. > > > > > > > > What I did find out since last posting is that the issue is not > > > > related to re-registering. Once incoming calls do not work anymore, > > > > even if I manually go to accounts de-register, register, incoming > > > > calls still do not work. I have to completely shutdown Ekiga and start > > > > it up again for it to work. > > > > > > > > Will post back results. > > > > > > > > > > What about twinkle, are you using STUN with twinkle or not ? > > > > > > Also, could you post a -d 4 output to pastebin with a call attempt ? > > > > > > > > > > > > > > OK, I believe I am starting to understand what is happening. My > > Router (Netgear DGN2000) has the feature SIP ALG enabled. If I > > disable that, then primarily testing shows that Ekiga is stable with > > incoming calls. The reason that twinkle works with SIP ALG enabled > > is that there is an option selected called "NAT traversal not > > needed" which has been selected. To be complete, Twinkle has 3 > > options: > > > > -1 NAT Traversal not needed > > -2 Use statically configured public IP address. (and an ip address > > can be entered) > > -3 Use STUN. (and a STUN server can be entered) > > > > OK, so now I have enabled this SIP ALG and disabled STUN with Ekiga, > > but no incoming calls now. > > > > The way I disabled STUN is to remove the value in > > key /apps/ekiga/general/nat/stun_server (make it blank). Is that the > > correct way? > > > > I would prefer to run Ekiga without STUN. Any additional I can set > > to disable the NAT traversal in Ekiga? > > > > Btw, my testing on Windows and Fedora 10 64 bit have the same > > results, which is good! > > > > OK, I have set SIP ALG to enabled, rebooted the router and removed > the STUN value. I am getting incoming calls now with Ekiga. Now > testing if it is stable. Ok, all appears to be stable now. Connected without STUN, SIP ALG enabled and connected for > 1 hour now. As a tip, perhaps it is handy to put the STUN switch in the GUI rather than as a config item in gconf-editor which is more difficult to edit. On Windows for instance, there is no gconf-editor, so have no idea how to disable the STUN server for the Ekiga Windows port. Thanks for you help in getting this resolved Damien! Much appreciated. Keep up the good Ekiga work! -------------- next part -------------- An HTML attachment was scrubbed... URL: From leamas.alec at gmail.com Sun Feb 15 16:45:12 2009 From: leamas.alec at gmail.com (Alec Leamas) Date: Sun, 15 Feb 2009 17:45:12 +0100 Subject: [Ekiga-list] Hacking: ekiga-callto: Yet another update In-Reply-To: <499150C8.8080503@pu-pm.univ-fcomte.fr> References: <1233647706.3413.1298206689@webmail.messagingengine.com> <1233682734.18030.37.camel@achille> <1233686408.5192.1.camel@scorpion.multitel.be> <1233741347.19079.1298445445@webmail.messagingengine.com> <1233774520.4593.4.camel@scorpion.multitel.be> <1233850723.32479.1298726781@webmail.messagingengine.com> <498B717B.5000603@gmail.com> <1233998959.4242.3.camel@scorpion.multitel.be> <1234203228.8086.6.camel@achille> <4990B712.3020701@gmail.com> <499150C8.8080503@pu-pm.univ-fcomte.fr> Message-ID: <49984698.2040600@gmail.com> Ive dropped new RPM:s and tarball at ftp://mumin.dnsalias.net/pub/ekiga-callto. From the changelog: * Sat Feb 14 2009 Alec Leamas 0.2.13-1 - New dialog for editing ambiguous numbers before calling. - Installed new testpage: http://mumin.dnsalias.net/numberformats.html - Improved number identification. - New versioning scheme, svn-versioned tarballs. - Suse (11.2) and Mandriva (2009.9) RPM support. The big news is a dialog giving user a chance to review the guess the system does. The number recognition has also improved a lot. There s also a single javascript file. This should work on Windows, will convert phone numbers into links. However, this means that users are on their own to find an application which can handle the callto: URL:s. Unfortunately, Ekiga as of today is not such an application. Feedback welcome. As always, need help with localisations. I'm also interested in URL:s containing phone numbers which are not handled correct. Thr README (big update) has information about new build instructions, perfomance etc. Cheers! --alec Eugen Dedu wrote: > About the phone number format, is > http://wiki.ekiga.org/index.php/API::GmContact::PhoneNumbers useful to > you? From f.vonbock at gmail.com Sun Feb 15 20:10:11 2009 From: f.vonbock at gmail.com (Ali) Date: Sun, 15 Feb 2009 23:10:11 +0300 Subject: [Ekiga-list] Support for use ekiga softphone In-Reply-To: <4992F3FB.4030004@pu-pm.univ-fcomte.fr> References: <1234366648.8469.11.camel@ubuntu.ubuntu-domain> <4992F3FB.4030004@pu-pm.univ-fcomte.fr> Message-ID: <499876A3.4070605@gmail.com> Eugen Dedu wrote: > Heou wrote: >> Dear all, >> >> I have a problem when I use the ekiga softphone. From Edit/Account, I >> add new account and check on the box in the first column, I receive a >> notice in the status column: Registration failed: timeout. >> And I cannot use it. >> Could anyone help me to fix this error? > > Could you restart ekiga? > i have the same problem, i've been looking for a solution for more than 3 months now, i've tried xp, ubuntu gutsy, ubuntu hardy, eebuntu 8.10, and i get the same result. it might be a router issue or something (in terms that your router might not support sip) who knows..i hope you find a solution From dsandras at seconix.com Sun Feb 15 20:57:29 2009 From: dsandras at seconix.com (Damien Sandras) Date: Sun, 15 Feb 2009 21:57:29 +0100 Subject: [Ekiga-list] Feature request: stop screensaver In-Reply-To: References: Message-ID: <1234731449.6874.0.camel@scorpion.multitel.be> Hi, Le samedi 14 f?vrier 2009 ? 19:31 +0000, Andrea a ?crit : > Hi, > > I would like to know whether other people would be interested in adding a config flag to stop the > screensaver during a video call. I think it should not be a config flag : by default, it should stop the screensaver when being in a call. > I wanted to try to add id myself I and I found that there is a call to reset the counter > XResetScreensaver. > > I would like to ask the developers if there is an easy point in the code that is called often during > a call. I would add later the relevant config option. > I think there is also a standard DBUS call for that, but I'm not sure about 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 Feb 15 20:58:32 2009 From: dsandras at seconix.com (Damien Sandras) Date: Sun, 15 Feb 2009 21:58:32 +0100 Subject: [Ekiga-list] ekiga 3 and 16bpp displays In-Reply-To: References: <1234608102.4280.4.camel@scorpion.multitel.be> Message-ID: <1234731512.6874.3.camel@scorpion.multitel.be> Le dimanche 15 f?vrier 2009 ? 14:14 +0100, Olivier Blin a ?crit : > Damien Sandras writes: > > > Le vendredi 13 f?vrier 2009 ? 18:35 +0100, Olivier Blin a ?crit : > >> Hello, > >> > >> I have a crash with ekiga (3.0.x or 3.1.x) when using a 16bpp display. > >> Here is an interesting pointer in the trace: > >> Could not find visual with colordepth of 24 bits per pixel > >> > >> It seems that XWindow::checkDepth() fallbacks to 24bpp, but it does not > >> support 16bpp. > >> > >> The log + trace can be found here: > >> http://people.mandriva.com/~blino/ekiga-crash-16bpp.log > >> > >> Is ekiga supposed to work with only 24bpp and 32bpp displays? > > > > I think so yes. > > > >> What can be done to make it work on 16bpp displays? > > > > Fix the code so that it works with 16bpp too :-) > > Ok, so it mostly needs to be implemented in ptlib? > > That would mean: > - in ptlib, src/ptlib/common/vconvert.cxx: > o add support for RGB565 in PStandardColourConverter::YUV420PtoRGB() > o add wrappers for this RGB565 mode > - in ekiga, lib/gui/xwindow.cpp: > o add a new xFormats entry: > {"RGB16", 16, 2, LSBFirst, 0x0000F800, 0x000007E0, 0x0000001F}, > o fallback to 16bpp in XWindow::checkDepth() when appropriate > > Does it sound sensible? > It seems so. It should be implemented in ptlib (for the conversion) and in the display code (in Ekiga : xvideo, x11 and directdraw, ie at 3 places). -- _ 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 Feb 15 20:59:39 2009 From: dsandras at seconix.com (Damien Sandras) Date: Sun, 15 Feb 2009 21:59:39 +0100 Subject: [Ekiga-list] Hacking: ekiga-callto: Yet another update In-Reply-To: <49984698.2040600@gmail.com> References: <1233647706.3413.1298206689@webmail.messagingengine.com> <1233682734.18030.37.camel@achille> <1233686408.5192.1.camel@scorpion.multitel.be> <1233741347.19079.1298445445@webmail.messagingengine.com> <1233774520.4593.4.camel@scorpion.multitel.be> <1233850723.32479.1298726781@webmail.messagingengine.com> <498B717B.5000603@gmail.com> <1233998959.4242.3.camel@scorpion.multitel.be> <1234203228.8086.6.camel@achille> <4990B712.3020701@gmail.com> <499150C8.8080503@pu-pm.univ-fcomte.fr> <49984698.2040600@gmail.com> Message-ID: <1234731579.6874.7.camel@scorpion.multitel.be> Le dimanche 15 f?vrier 2009 ? 17:45 +0100, Alec Leamas a ?crit : > Ive dropped new RPM:s and tarball at > ftp://mumin.dnsalias.net/pub/ekiga-callto. From the changelog: > > * Sat Feb 14 2009 Alec Leamas 0.2.13-1 > - New dialog for editing ambiguous numbers before calling. > - Installed new testpage: > http://mumin.dnsalias.net/numberformats.html > - Improved number identification. > - New versioning scheme, svn-versioned tarballs. > - Suse (11.2) and Mandriva (2009.9) RPM support. > > The big news is a dialog giving user a chance to review the guess the > system does. The number recognition has also improved a lot. > > There s also a single javascript file. This should work on Windows, will > convert phone numbers into links. However, this means that users are on > their own to find an application which can handle the callto: URL:s. > Unfortunately, Ekiga as of today is not such an application. > > Feedback welcome. As always, need help with localisations. I'm also > interested in URL:s containing phone numbers which are not handled > correct. Thr README (big update) has information about new build > instructions, perfomance etc. Thanks for this! -- _ 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 Feb 15 21:00:37 2009 From: dsandras at seconix.com (Damien Sandras) Date: Sun, 15 Feb 2009 22:00:37 +0100 Subject: [Ekiga-list] Support for use ekiga softphone In-Reply-To: <499876A3.4070605@gmail.com> References: <1234366648.8469.11.camel@ubuntu.ubuntu-domain> <4992F3FB.4030004@pu-pm.univ-fcomte.fr> <499876A3.4070605@gmail.com> Message-ID: <1234731637.6874.9.camel@scorpion.multitel.be> Le dimanche 15 f?vrier 2009 ? 23:10 +0300, Ali a ?crit : > Eugen Dedu wrote: > > Heou wrote: > >> Dear all, > >> > >> I have a problem when I use the ekiga softphone. From Edit/Account, I > >> add new account and check on the box in the first column, I receive a > >> notice in the status column: Registration failed: timeout. > >> And I cannot use it. > >> Could anyone help me to fix this error? > > > > Could you restart ekiga? > > > i have the same problem, i've been looking for a solution for more than > 3 months now, i've tried xp, ubuntu gutsy, ubuntu hardy, eebuntu 8.10, > and i get the same result. > > it might be a router issue or something (in terms that your router might > not support sip) > who knows..i hope you find a solution See the thread from Bas Driessen, maybe it helps. -- _ 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 chinku.linux at gmail.com Mon Feb 16 05:56:37 2009 From: chinku.linux at gmail.com (chaitanya mehandru) Date: Mon, 16 Feb 2009 11:26:37 +0530 Subject: [Ekiga-list] Dump FPS from ekiga 3.0.2 to a file In-Reply-To: <49969D52.5040603@pu-pm.univ-fcomte.fr> References: <24b40b2b0902122243p490da840p2a14585f7f6b8bdf@mail.gmail.com> <49969D52.5040603@pu-pm.univ-fcomte.fr> Message-ID: <24b40b2b0902152156s175070efoe200070807c2ef5f@mail.gmail.com> Thanks for you reply. I expected that I might need to change the code!! On Sat, Feb 14, 2009 at 4:00 PM, Eugen Dedu wrote: > chaitanya mehandru wrote: > >> Hi, Is there a way to record the FPS from ekiga and dump it to a file >> for >> taking an average FPS reading? >> > > I think the only solution is to modify the ekiga code yourself. > > -- > Eugen > _______________________________________________ > 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 hb at h-bauer.de Mon Feb 16 08:21:35 2009 From: hb at h-bauer.de (Hans Bauer) Date: Mon, 16 Feb 2009 09:21:35 +0100 Subject: [Ekiga-list] Ekiga 3.02 for Windows: Logitech QuickCam Pro9000 and choosing Default-SIP ? Message-ID: <4999220F.1000305@h-bauer.de> Hello and thank you a lot for the great program and windows port. During installation of Ekiga 3.02 for Windows (the release version) my Logitech QuickCam Pro9000 webcam was no more recognized as it was with Ekiga 2.0.11 beta for windows. My System is WinXP Prof. SP 3. The webcam works fine with Skype and the drivers of the webcam are updated. Skype was not open during the installation of Ekiga 3.02. Looking into the configuration immediately after the installation of Ekiga, i could choose from - Microsoft WDM Image Capture (Win32) (PTLi.. - Moving Logo (Moving Logo(Movin Logo) and the Logitech webcam was greyed out. Meanwhile the Logitech is deleted from the list and searching for a webcam device does not bring it back. Is there any possiblity to use my webcam with Ekiga 3.02 for Windows? Working with Ekiga 2.0.11 beta for Windows it was possible to choose a default sip account, which was shown bolt in the list. I'm registering 3 sip-accounts the same time. With Ekiga 3.02 for Windows, i no more find a Default-Button for this purpose. Also i was not able to find any other possibility to set a default account. Any idea? Thousand thanks for any efforts. Yours, Hans Bauer -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: hb.vcf Type: text/x-vcard Size: 739 bytes Desc: not available URL: From dsandras at seconix.com Mon Feb 16 09:07:41 2009 From: dsandras at seconix.com (Damien Sandras) Date: Mon, 16 Feb 2009 10:07:41 +0100 Subject: [Ekiga-list] Ekiga 3.02 for Windows: Logitech QuickCam Pro9000 and choosing Default-SIP ? In-Reply-To: <4999220F.1000305@h-bauer.de> References: <4999220F.1000305@h-bauer.de> Message-ID: <1234775261.4340.12.camel@scorpion.multitel.be> Le lundi 16 f?vrier 2009 ? 09:21 +0100, Hans Bauer a ?crit : > Hello and thank you a lot for the great program and windows port. > > During installation of Ekiga 3.02 for Windows (the release version) my > Logitech QuickCam Pro9000 webcam was no more recognized as it was with > Ekiga 2.0.11 beta for windows. My System is WinXP Prof. SP 3. The > webcam works fine with Skype and the drivers of the webcam are > updated. Skype was not open during the installation of Ekiga 3.02. > Looking into the configuration immediately after the installation of > Ekiga, i could choose from > - Microsoft WDM Image Capture (Win32) (PTLi.. > - Moving Logo (Moving Logo(Movin Logo) > and the Logitech webcam was greyed out. Meanwhile the Logitech is > deleted from the list and searching for a webcam device does not bring > it back. Is there any possiblity to use my webcam with Ekiga 3.02 for > Windows? I can't answer to this question, but perhaps someone else will. > Working with Ekiga 2.0.11 beta for Windows it was possible to choose a > default sip account, which was shown bolt in the list. I'm registering > 3 sip-accounts the same time. With Ekiga 3.02 for Windows, i no more > find a Default-Button for this purpose. Also i was not able to find > any other possibility to set a default account. Any idea? It has been removed, but there is now autocompletion, meaning that if you enter sip:123456@, it will propose you a drop down with the list of possible accounts to choose from. -- _ 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 Feb 16 09:08:32 2009 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Mon, 16 Feb 2009 10:08:32 +0100 Subject: [Ekiga-list] Ekiga 3.02 for Windows: Logitech QuickCam Pro9000 and choosing Default-SIP ? In-Reply-To: <4999220F.1000305@h-bauer.de> References: <4999220F.1000305@h-bauer.de> Message-ID: <49992D10.8030001@pu-pm.univ-fcomte.fr> Hans Bauer wrote: > Working with Ekiga 2.0.11 beta for Windows it was possible to choose a > default sip account, which was shown bolt in the list. I'm registering 3 > sip-accounts the same time. With Ekiga 3.02 for Windows, i no more find > a Default-Button for this purpose. Also i was not able to find any other > possibility to set a default account. Any idea? I think it's the first account shown which is the default in ekiga 3. -- Eugen From dsandras at seconix.com Mon Feb 16 09:11:28 2009 From: dsandras at seconix.com (Damien Sandras) Date: Mon, 16 Feb 2009 10:11:28 +0100 Subject: [Ekiga-list] Ekiga 3.02 for Windows: Logitech QuickCam Pro9000 and choosing Default-SIP ? In-Reply-To: <49992D10.8030001@pu-pm.univ-fcomte.fr> References: <4999220F.1000305@h-bauer.de> <49992D10.8030001@pu-pm.univ-fcomte.fr> Message-ID: <1234775488.4340.14.camel@scorpion.multitel.be> Le lundi 16 f?vrier 2009 ? 10:08 +0100, Eugen Dedu a ?crit : > Hans Bauer wrote: > > Working with Ekiga 2.0.11 beta for Windows it was possible to choose a > > default sip account, which was shown bolt in the list. I'm registering 3 > > sip-accounts the same time. With Ekiga 3.02 for Windows, i no more find > > a Default-Button for this purpose. Also i was not able to find any other > > possibility to set a default account. Any idea? > > I think it's the first account shown which is the default in ekiga 3. > In 3.20. -- _ 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 Feb 16 09:49:54 2009 From: dsandras at seconix.com (Damien Sandras) Date: Mon, 16 Feb 2009 10:49:54 +0100 Subject: [Ekiga-list] Ekiga 3.02 for Windows: Logitech QuickCam Pro9000 and choosing Default-SIP ? In-Reply-To: <49993238.6060609@h-bauer.de> References: <4999220F.1000305@h-bauer.de> <1234775261.4340.12.camel@scorpion.multitel.be> <49993238.6060609@h-bauer.de> Message-ID: <1234777794.4340.35.camel@scorpion.multitel.be> Le lundi 16 f?vrier 2009 ? 10:30 +0100, Hans Bauer a ?crit : > Hello Damian, > > thank you a lot for your answer, my reply is at the bottom of the > mail: > > Damien Sandras wrote: > > Le lundi 16 f?vrier 2009 ? 09:21 +0100, Hans Bauer a ?crit : > > > > > Hello and thank you a lot for the great program and windows port. > > > > > > During installation of Ekiga 3.02 for Windows (the release version) my > > > Logitech QuickCam Pro9000 webcam was no more recognized as it was with > > > Ekiga 2.0.11 beta for windows. My System is WinXP Prof. SP 3. The > > > webcam works fine with Skype and the drivers of the webcam are > > > updated. Skype was not open during the installation of Ekiga 3.02. > > > Looking into the configuration immediately after the installation of > > > Ekiga, i could choose from > > > - Microsoft WDM Image Capture (Win32) (PTLi.. > > > - Moving Logo (Moving Logo(Movin Logo) > > > and the Logitech webcam was greyed out. Meanwhile the Logitech is > > > deleted from the list and searching for a webcam device does not bring > > > it back. Is there any possiblity to use my webcam with Ekiga 3.02 for > > > Windows? > > > > > > > I can't answer to this question, but perhaps someone else will. > > > > > > > Working with Ekiga 2.0.11 beta for Windows it was possible to choose a > > > default sip account, which was shown bolt in the list. I'm registering > > > 3 sip-accounts the same time. With Ekiga 3.02 for Windows, i no more > > > find a Default-Button for this purpose. Also i was not able to find > > > any other possibility to set a default account. Any idea? > > > > > > > It has been removed, but there is now autocompletion, meaning that if > > you enter sip:123456@, it will propose you a drop down with the list of > > possible accounts to choose from. Please do not reply off-list. > That is very impractical and i really miss the ability to chose a > default sip-provider. I parallel use 3 active sip-accounts, all > allowing pc to telefone calls. 90% of my calls go to the landline and > the telefone number is not qualified for autocompletion. So right now > i did not find a way using Ekiga e.g. to specify my first > sipgate-account to dial a landline number and to connect me with a > telefone. Do you know any help? > > With X-Lite i registrate at sipgate (the problem is: only 1 account) > and type in the telefone number. That's all and i am connected. If you use Ekiga 3.20 and have only one account, it will do the same. I also think that if you do not put anything, it will use the latest account you used. That means that if you dial more often through sipgate, it will autocomplete to sipgate for you. -- _ 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 hb at h-bauer.de Mon Feb 16 09:58:56 2009 From: hb at h-bauer.de (Hans Bauer) Date: Mon, 16 Feb 2009 10:58:56 +0100 Subject: [Ekiga-list] Ekiga 3.02 for Windows: Logitech QuickCam Pro9000 and choosing Default-SIP ? In-Reply-To: <1234777794.4340.35.camel@scorpion.multitel.be> References: <4999220F.1000305@h-bauer.de> <1234775261.4340.12.camel@scorpion.multitel.be> <49993238.6060609@h-bauer.de> <1234777794.4340.35.camel@scorpion.multitel.be> Message-ID: <499938E0.5060803@h-bauer.de> Damien Sandras wrote: > Le lundi 16 f?vrier 2009 ? 10:30 +0100, Hans Bauer a ?crit : > >> Hello Damian, >> >> thank you a lot for your answer, my reply is at the bottom of the >> mail: >> >> Damien Sandras wrote: >> >>> Le lundi 16 f?vrier 2009 ? 09:21 +0100, Hans Bauer a ?crit : >>> >>> >>>> Hello and thank you a lot for the great program and windows port. >>>> >>>> During installation of Ekiga 3.02 for Windows (the release version) my >>>> Logitech QuickCam Pro9000 webcam was no more recognized as it was with >>>> Ekiga 2.0.11 beta for windows. My System is WinXP Prof. SP 3. The >>>> webcam works fine with Skype and the drivers of the webcam are >>>> updated. Skype was not open during the installation of Ekiga 3.02. >>>> Looking into the configuration immediately after the installation of >>>> Ekiga, i could choose from >>>> - Microsoft WDM Image Capture (Win32) (PTLi.. >>>> - Moving Logo (Moving Logo(Movin Logo) >>>> and the Logitech webcam was greyed out. Meanwhile the Logitech is >>>> deleted from the list and searching for a webcam device does not bring >>>> it back. Is there any possiblity to use my webcam with Ekiga 3.02 for >>>> Windows? >>>> >>>> >>> I can't answer to this question, but perhaps someone else will. >>> >>> >>> >>>> Working with Ekiga 2.0.11 beta for Windows it was possible to choose a >>>> default sip account, which was shown bolt in the list. I'm registering >>>> 3 sip-accounts the same time. With Ekiga 3.02 for Windows, i no more >>>> find a Default-Button for this purpose. Also i was not able to find >>>> any other possibility to set a default account. Any idea? >>>> >>>> >>> It has been removed, but there is now autocompletion, meaning that if >>> you enter sip:123456@, it will propose you a drop down with the list of >>> possible accounts to choose from. >>> > > Please do not reply off-list. > Sorry, i did not recognize this. > >> That is very impractical and i really miss the ability to chose a >> default sip-provider. I parallel use 3 active sip-accounts, all >> allowing pc to telefone calls. 90% of my calls go to the landline and >> the telefone number is not qualified for autocompletion. So right now >> i did not find a way using Ekiga e.g. to specify my first >> sipgate-account to dial a landline number and to connect me with a >> telefone. Do you know any help? >> >> With X-Lite i registrate at sipgate (the problem is: only 1 account) >> and type in the telefone number. That's all and i am connected. >> > > If you use Ekiga 3.20 and have only one account, it will do the same. > I also think that if you do not put anything, it will use the latest > account you used. That means that if you dial more often through > sipgate, it will autocomplete to sipgate for you. > Thank you a lot. So i will wait until 3.20 for windows and hope for a explicit possibility to choose a sip-account for dial-out to landlines. As you can imagine, only 1 account will be a problem for me, for documentation and also for billing. My best wishes and thanks. Hans Bauer -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: hb.vcf Type: text/x-vcard Size: 762 bytes Desc: not available URL: From mike at cchtml.com Mon Feb 16 14:27:28 2009 From: mike at cchtml.com (Michael Cronenworth) Date: Mon, 16 Feb 2009 08:27:28 -0600 Subject: [Ekiga-list] Ekiga 3.02 for Windows: Logitech QuickCam Pro9000 and choosing Default-SIP ? In-Reply-To: <4999220F.1000305@h-bauer.de> References: <4999220F.1000305@h-bauer.de> Message-ID: <499977D0.9050803@cchtml.com> -------- Original Message -------- Subject: [Ekiga-list] Ekiga 3.02 for Windows: Logitech QuickCam Pro9000 and choosing Default-SIP ? From: Hans Bauer To: ekiga-list at gnome.org Date: 02/16/2009 02:21 AM > Is there any possiblity to use my webcam with Ekiga 3.02 for > Windows? > Microsoft WDM Image Capture is what you want. I, too, have a Logitech QuickCam 9000. From dsandras at seconix.com Mon Feb 16 14:39:27 2009 From: dsandras at seconix.com (Damien Sandras) Date: Mon, 16 Feb 2009 15:39:27 +0100 Subject: [Ekiga-list] Ekiga 3.02 for Windows: Logitech QuickCam Pro9000 and choosing Default-SIP ? In-Reply-To: <499977D0.9050803@cchtml.com> References: <4999220F.1000305@h-bauer.de> <499977D0.9050803@cchtml.com> Message-ID: <1234795167.3997.38.camel@scorpion.multitel.be> Le lundi 16 f?vrier 2009 ? 08:27 -0600, Michael Cronenworth a ?crit : > -------- Original Message -------- > Subject: [Ekiga-list] Ekiga 3.02 for Windows: Logitech QuickCam Pro9000 > and choosing Default-SIP ? > From: Hans Bauer > To: ekiga-list at gnome.org > Date: 02/16/2009 02:21 AM > > > > Is there any possiblity to use my webcam with Ekiga 3.02 for > > Windows? > > > > Microsoft WDM Image Capture is what you want. I, too, have a Logitech > QuickCam 9000. Notice taht there should also be a way to activate DirectVideo input. -- _ 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 hb at h-bauer.de Mon Feb 16 14:57:45 2009 From: hb at h-bauer.de (Hans Bauer) Date: Mon, 16 Feb 2009 15:57:45 +0100 Subject: [Ekiga-list] Ekiga 3.02 for Windows: Logitech QuickCam Pro9000 and choosing Default-SIP ? In-Reply-To: <499977D0.9050803@cchtml.com> References: <4999220F.1000305@h-bauer.de> <499977D0.9050803@cchtml.com> Message-ID: <49997EE9.1070500@h-bauer.de> Michael Cronenworth wrote: > -------- Original Message -------- > Subject: [Ekiga-list] Ekiga 3.02 for Windows: Logitech QuickCam > Pro9000 and choosing Default-SIP ? > From: Hans Bauer > To: ekiga-list at gnome.org > Date: 02/16/2009 02:21 AM > > >> Is there any possiblity to use my webcam with Ekiga 3.02 for Windows? >> > > Microsoft WDM Image Capture is what you want. I, too, have a Logitech > QuickCam 9000. > > > Michael, thank you. I already tried to choose Microsoft WDM Image Capture but got an access error stating that my video device already is used by another application, but it isn't. I previously shut down x-lite and even WinTV (Hauppauge). No other application on my pc is able to utilize video. After the statement is closed i'm also asked for sufficient rights for the video device "Microsoft WDM Image Capture" but i am already working as admin. Closing ekiga and opening the logitech webcam application shows that the webcam is working properly (all drivers installed). -------------- next part -------------- A non-text attachment was scrubbed... Name: hb.vcf Type: text/x-vcard Size: 739 bytes Desc: not available URL: From hb at h-bauer.de Mon Feb 16 15:04:51 2009 From: hb at h-bauer.de (Hans Bauer) Date: Mon, 16 Feb 2009 16:04:51 +0100 Subject: [Ekiga-list] Ekiga 3.02 for Windows: Logitech QuickCam Pro9000 and choosing Default-SIP ? In-Reply-To: <1234795167.3997.38.camel@scorpion.multitel.be> References: <4999220F.1000305@h-bauer.de> <499977D0.9050803@cchtml.com> <1234795167.3997.38.camel@scorpion.multitel.be> Message-ID: <49998093.4060403@h-bauer.de> Damien Sandras wrote: > Le lundi 16 f?vrier 2009 ? 08:27 -0600, Michael Cronenworth a ?crit : > >> -------- Original Message -------- >> Subject: [Ekiga-list] Ekiga 3.02 for Windows: Logitech QuickCam Pro9000 >> and choosing Default-SIP ? >> From: Hans Bauer >> To: ekiga-list at gnome.org >> Date: 02/16/2009 02:21 AM >> >> >> >>> Is there any possiblity to use my webcam with Ekiga 3.02 for >>> Windows? >>> >>> >> Microsoft WDM Image Capture is what you want. I, too, have a Logitech >> QuickCam 9000. >> > > Notice taht there should also be a way to activate DirectVideo input. > Hello Damien. Could you please explain me what "activate DirectVideo input" means? Do i have to activate DirectVideo within Ekiga and what is it? Thanks a lot and please excuse my untaught question. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: hb.vcf Type: text/x-vcard Size: 762 bytes Desc: not available URL: From jpuydt at free.fr Mon Feb 16 15:51:16 2009 From: jpuydt at free.fr (Julien Puydt) Date: Mon, 16 Feb 2009 16:51:16 +0100 Subject: [Ekiga-list] Feature request: stop screensaver In-Reply-To: <1234731449.6874.0.camel@scorpion.multitel.be> References: <1234731449.6874.0.camel@scorpion.multitel.be> Message-ID: <49998B74.2030107@free.fr> Damien Sandras a ?crit : > Le samedi 14 f?vrier 2009 ? 19:31 +0000, Andrea a ?crit : >> Hi, >> >> I would like to know whether other people would be interested in adding a config flag to stop the >> screensaver during a video call. > > I think it should not be a config flag : by default, it should stop the > screensaver when being in a call. > >> I wanted to try to add id myself I and I found that there is a call to reset the counter >> XResetScreensaver. >> >> I would like to ask the developers if there is an easy point in the code that is called often during >> a call. I would add later the relevant config option. > > I think there is also a standard DBUS call for that, but I'm not sure > about that. It's already working, as part of gnome-session support since 20090129. Snark on #ekiga From mariofutire at googlemail.com Mon Feb 16 21:03:24 2009 From: mariofutire at googlemail.com (Andrea) Date: Mon, 16 Feb 2009 21:03:24 +0000 Subject: [Ekiga-list] Feature request: stop screensaver In-Reply-To: <49998B74.2030107@free.fr> References: <1234731449.6874.0.camel@scorpion.multitel.be> <49998B74.2030107@free.fr> Message-ID: Julien Puydt wrote: > Damien Sandras a ?crit : > >> >> I think there is also a standard DBUS call for that, but I'm not sure >> about that. I spent some time reading on Internet and it does not seem to exist a unique way of stopping all existing screensavers (KDE 3, 4, xscreensaver, no idea about gnome). > > It's already working, as part of gnome-session support since 20090129. > I look forward to using this feature in a new release of ekiga. Andrea From hb at h-bauer.de Tue Feb 17 06:03:06 2009 From: hb at h-bauer.de (Hans Bauer) Date: Tue, 17 Feb 2009 07:03:06 +0100 Subject: [Ekiga-list] Ekiga 3.02 for Windows: Logitech QuickCam Pro9000 and choosing Default-SIP ? In-Reply-To: <49997EE9.1070500@h-bauer.de> References: <4999220F.1000305@h-bauer.de> <499977D0.9050803@cchtml.com> <49997EE9.1070500@h-bauer.de> Message-ID: <499A531A.5040208@h-bauer.de> Hans Bauer wrote: > Michael Cronenworth wrote: > >> -------- Original Message -------- >> Subject: [Ekiga-list] Ekiga 3.02 for Windows: Logitech QuickCam >> Pro9000 and choosing Default-SIP ? >> From: Hans Bauer >> To: ekiga-list at gnome.org >> Date: 02/16/2009 02:21 AM >> >> >> >>> Is there any possiblity to use my webcam with Ekiga 3.02 for Windows? >>> >>> >> Microsoft WDM Image Capture is what you want. I, too, have a Logitech >> QuickCam 9000. >> >> >> >> > Michael, thank you. I already tried to choose Microsoft WDM Image > Capture but got an access error stating that my video device already is > used by another application, but it isn't. I previously shut down x-lite > and even WinTV (Hauppauge). No other application on my pc is able to > utilize video. After the statement is closed i'm also asked for > sufficient rights for the video device "Microsoft WDM Image Capture" but > i am already working as admin. Closing ekiga and opening the logitech > webcam application shows that the webcam is working properly (all > drivers installed). > Since today, after choosing Microsoft WDM Image Capture, my PC crashes each time i start and activate Ekiga 3.02 for Windows. I had to deinstall Ekiga. Sorry, but i will have to switch back to 2.0.11-beta until 3.20 is out to try. Thanks for your support and my best wishes. Hans Bauer -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: hb.vcf Type: text/x-vcard Size: 739 bytes Desc: not available URL: From f.vonbock at gmail.com Tue Feb 17 21:13:11 2009 From: f.vonbock at gmail.com (Fedor vonBock) Date: Wed, 18 Feb 2009 00:13:11 +0300 Subject: [Ekiga-list] ekiga timeout - eeebuntu Message-ID: hi, i'm trying to use ekiga on my new laptop (eee) but this registration failed message always appears i run ekiga -d 4 in the command prompt and here's the log from the beginning up until it says registration timeout what do you think? ; i have submitted another mail with the same issue, but i've shortened the log in order to fit the maximum size allocated, i wasn't able to cancel that post note 2009/02/13 14:36:11.541 0:01.088 ekiga PWLib File handle high water mark set: 26 PUDPSocket (ekiga:9288): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated (ekiga:9288): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated (ekiga:9288): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated (ekiga:9288): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated (ekiga:9288): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated 2009/02/13 14:36:13.031 0:02.578 ekiga Ekiga version 2.0.12 2009/02/13 14:36:13.033 0:02.580 ekiga OPAL version 2.2.11 2009/02/13 14:36:13.034 0:02.581 ekiga PWLIB version 1.10.10 2009/02/13 14:36:13.036 0:02.583 ekiga GNOME support enabled 2009/02/13 14:36:13.037 0:02.585 ekiga Fullscreen support enabled 2009/02/13 14:36:13.039 0:02.586 ekiga DBUS support enabled 2009/02/13 14:36:13.047 0:02.594 ekiga PWLib File handle high water mark set: 38 PUDPSocket 2009/02/13 14:36:13.057 0:02.619 ekiga Set TCP port range to 30000:30010 2009/02/13 14:36:13.073 0:02.620 ekiga Set RTP port range to 5000:5059 2009/02/13 14:36:13.073 0:02.620 ekiga Set UDP port range to 5060:5100 2009/02/13 14:36:13.074 0:02.621 ekiga OpalEP Created endpoint: h323 2009/02/13 14:36:13.074 0:02.621 ekiga H323 Created endpoint. 2009/02/13 14:36:13.081 0:02.629 ekiga OpalMan Added route "pc:.*=h323:" 2009/02/13 14:36:13.083 0:02.630 ekiga OpalEP Created endpoint: sip 2009/02/13 14:36:13.084 0:02.632 ekiga SIP Created endpoint. 2009/02/13 14:36:13.086 0:02.633 ekiga OpalMan Added route "pc:.*=sip:" 2009/02/13 14:36:13.087 0:02.634 ekiga OpalEP Created endpoint: pc 2009/02/13 14:36:13.089 0:02.637 ekiga PCSS Created PC sound system endpoint. 2009/02/13 14:36:13.096 0:02.643 ekiga OpalMan Added route "h323:.*=pc:" 2009/02/13 14:36:13.096 0:02.643 ekiga OpalMan Added route "sip:.*=pc:" 2009/02/13 14:36:13.362 0:02.910 ekiga PWLib File handle high water mark set: 40 Thread unblock pipe 2009/02/13 14:36:13.364 0:02.912 ekiga PWLib Thread high water mark set: 4 2009/02/13 14:36:13.366 0:02.913 Opal Listener:8c63730 Listen Started listening thread on tcp$192.168.1.7:1720 2009/02/13 14:36:13.367 0:02.914 Opal Listener:8c63730 Listen Waiting on socket accept on tcp$192.168.1.7:1720 2009/02/13 14:36:13.369 0:02.916 ekiga PWLib File handle high water mark set: 41 PUDPSocket 2009/02/13 14:36:13.371 0:02.918 ekiga PWLib File handle high water mark set: 42 PUDPSocket 2009/02/13 14:36:13.380 0:02.927 ekiga PWLib File handle high water mark set: 44 Thread unblock pipe 2009/02/13 14:36:13.382 0:02.929 ekiga PWLib Thread high water mark set: 5 2009/02/13 14:36:13.383 0:02.930 Opal Listener:8c64978 Listen Started listening thread on udp$192.168.1.7:5060 2009/02/13 14:36:13.384 0:02.931 Opal Listener:8c64978 Listen Waiting on UDP packet on udp$192.168.1.7:5060 2009/02/13 14:36:13.427 0:02.975 ekiga AVAHI Adding service Ali Khalfan 2009/02/13 14:36:13.451 0:03.011 ekiga PWLib File handle high water mark set: 47 Thread unblock pipe 2009/02/13 14:36:13.478 0:03.025 ekiga PWLib Thread high water mark set: 6 2009/02/13 14:36:13.929 0:03.476 GMAccounts...t:08c67718 PWLib File handle high water mark set: 49 Thread unblock pipe 2009/02/13 14:36:13.932 0:03.479 GMAccounts...t:08c67718 PWLib Thread high water mark set: 7 2009/02/13 14:36:13.954 0:03.502 Housekeeper PWLib File handle high water mark set: 50 PTCPSocket 2009/02/13 14:36:13.981 0:03.528 GMStunClient:08d0cf00 PWLib File handle high water mark set: 51 PTCPSocket 2009/02/13 14:36:14.337 0:03.884 GMStunClient:08d0cf00 PWLib File handle high water mark set: 52 PUDPSocket 2009/02/13 14:36:14.610 0:04.157 GMStunClient:08d0cf00 PWLib File handle low water mark set: 50 PUDPSocket 2009/02/13 14:36:20.133 0:09.680 GMStunClient:08d0cf00 OPAL STUN server "stun.ekiga.net" replies Symmetric NAT, external IP 89.148.39.209 2009/02/13 14:36:20.186 0:09.733 GMAccounts...t:08c67718 OpalUDP Binding to interface: 192.168.1.7:51481 2009/02/13 14:36:20.186 0:09.733 GMAccounts...t:08c67718 SIP Created transport udp$0.0.0.0 2009/02/13 14:36:20.186 0:09.733 GMAccounts...t:08c67718 OpalUDP Started connect to 86.64.162.35:5060 2009/02/13 14:36:20.451 0:09.998 GMAccounts...t:08c67718 OpalUDP STUN created socket: 89.148.39.209:5063 2009/02/13 14:36:20.452 0:09.999 SIP Transport:8d3aa78 SIP Read thread started. 2009/02/13 14:36:20.452 0:09.999 SIP Transport:8d3aa78 SIP Waiting for PDU on udp$86.64.162.35:5060 2009/02/13 14:36:20.452 0:10.000 GMAccounts...t:08c67718 SIP Created Transport for Registrar udp$86.64.162.35:5060 2009/02/13 14:36:20.454 0:10.001 GMAccounts...t:08c67718 PWLib File handle high water mark set: 53 PUDPSocket 2009/02/13 14:36:20.457 0:10.004 GMAccounts...t:08c67718 SIP Sending PDU on udp$86.64.162.35:5060 REGISTER sip:ekiga.net SIP/2.0 CSeq: 1 REGISTER Via: SIP/2.0/UDP 89.148.39.209:5063;branch= z9hG4bK2e5ef133-30f8-dd11-9ed2-0015afe7d424;rport User-Agent: Ekiga/2.0.12 From: >;tag=8453f133-30f8-dd11-9ed2-0015afe7d424 Call-ID: bc26c833-30f8-dd11-9ed2-0015afe7d424 at khalfan-laptop To: > Contact: Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Expires: 3600 Content-Length: 0 Max-Forwards: 70 -------------- next part -------------- An HTML attachment was scrubbed... URL: From cgundog at teknobil.com.tr Wed Feb 18 07:19:50 2009 From: cgundog at teknobil.com.tr (cgundog at teknobil.com.tr) Date: Wed, 18 Feb 2009 09:19:50 +0200 (EET) Subject: [Ekiga-list] Dtmf from analog voice Message-ID: <49860.81.214.86.55.1234941590.squirrel@mail.teknobil.com.tr> I have an analog voice interfaced with sip server through the codec. How can I have my analog voice interact with the sip server using dtmf tones? asteriks does not recognize my dtmf tones since it does not take the connection through the codec as a sip client. Cengiz G?ndo? Embedded Software Developer Teknobil Inc, From epetxepe at gmail.com Wed Feb 18 16:12:53 2009 From: epetxepe at gmail.com (Epelde Gorka) Date: Wed, 18 Feb 2009 17:12:53 +0100 Subject: [Ekiga-list] Trouble using Ekiga Win32 with Bonjour Message-ID: <5ca9a62d0902180812n7f213c46x3cd7551beb99fbf0@mail.gmail.com> Hi all, Following http://www.mail-archive.com/ekiga-list at gnome.org/msg05245.htmlemail, I've tried to use bonjour (apple) with latest win32 release http://www.pateam.org/archive/tmp/ekiga-win32/ekiga-setup-3.0.2-gtk-2.14.7.exe Both machines are running Vista. I've been able to find my network printer with the bonjour application that comes with the installation, so I think bonjour is installed correctly in both machines. Does this release include zeroconf functionalities? If not if there any build of 3.0.2 for win32 with zeroconf support? I was thinking in using bonjour, since I'm thinking to deploy Ekiga with my platform and i'm not going to have access to the router in all scenarios. So port forwarding or sipproxyd is not a good solution for me. Do you think that tunneling through http proxy would work with a proxy running in the internet (not in my internal network)? So that I would have a bad performance but a workaround, for symmetric NAT and bonjour issue? Thanks in advance, Gorka -------------- next part -------------- An HTML attachment was scrubbed... URL: From michel.memeteau at gmail.com Wed Feb 18 16:28:11 2009 From: michel.memeteau at gmail.com (michel memeteau) Date: Wed, 18 Feb 2009 17:28:11 +0100 Subject: [Ekiga-list] Trouble using Ekiga Win32 with Bonjour In-Reply-To: <5ca9a62d0902180812n7f213c46x3cd7551beb99fbf0@mail.gmail.com> References: <5ca9a62d0902180812n7f213c46x3cd7551beb99fbf0@mail.gmail.com> Message-ID: Hi On Wed, Feb 18, 2009 at 5:12 PM, Epelde Gorka wrote: > I was thinking in using bonjour, since I'm thinking to deploy Ekiga with > my platform and i'm not going to have access to the router in all scenarios. > So port forwarding or sipproxyd is not a good solution for me. > I m not sure I understood this : you think about Bonjour as a tool for Nat traversal ? Bonjour is made to detact other SIp clients inside the Nat, it can't do anything about the outside world. -------------- next part -------------- An HTML attachment was scrubbed... URL: From epetxepe at gmail.com Wed Feb 18 16:51:52 2009 From: epetxepe at gmail.com (Epelde Gorka) Date: Wed, 18 Feb 2009 17:51:52 +0100 Subject: [Ekiga-list] Trouble using Ekiga Win32 with Bonjour In-Reply-To: References: <5ca9a62d0902180812n7f213c46x3cd7551beb99fbf0@mail.gmail.com> Message-ID: <5ca9a62d0902180851v2a475a4dna7d6a39aad4e0aab@mail.gmail.com> 2009/2/18 michel memeteau > Hi > > On Wed, Feb 18, 2009 at 5:12 PM, Epelde Gorka wrote: > >> I was thinking in using bonjour, since I'm thinking to deploy Ekiga with >> my platform and i'm not going to have access to the router in all scenarios. >> So port forwarding or sipproxyd is not a good solution for me. >> > > I m not sure I understood this : you think about Bonjour as a tool for Nat > traversal ? > No. I'm thinking in a scenario where I would have clients different clients behind a NAT, but not limited to NAT clients. In http://wiki.ekiga.org/index.php/Ekiga_behind_a_NAT_router#I_have_2_Ekiga_behind_a_NAT_using_STUN:_they_can.27t_communicateit proposes two solutions to be able to correctly communicate clients behind a NAT. In my case, zeroconf in their corresponding implementations (avahi, bonjour) would be the best option, since the second option of using SIPProxyd needs access to the router/firewall (as far as i understand) and I might not have access to the router in all scenarios. Do you have any build of Ekiga Win32 3.0.2 working with bonjour? > > Bonjour is made to detact other SIp clients inside the Nat, it can't do > anything about the outside world. > Yes that's how I understand Bonjour. > > _______________________________________________ > 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 Wed Feb 18 17:23:56 2009 From: dsandras at seconix.com (Damien Sandras) Date: Wed, 18 Feb 2009 18:23:56 +0100 Subject: [Ekiga-list] Dtmf from analog voice In-Reply-To: <49860.81.214.86.55.1234941590.squirrel@mail.teknobil.com.tr> References: <49860.81.214.86.55.1234941590.squirrel@mail.teknobil.com.tr> Message-ID: <1234977836.11150.20.camel@scorpion.multitel.be> Le mercredi 18 f?vrier 2009 ? 09:19 +0200, cgundog at teknobil.com.tr a ?crit : > I have an analog voice interfaced with sip server through the codec. How > can I have my analog voice interact with the sip server using dtmf tones? > asteriks does not recognize my dtmf tones since it does not take the > connection through the codec as a sip client. Asterisk is supposed to do that for you : convert analog DTMFs to SIP DTMFs and vice-versa. I propose you ask your questions on their mailing 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 Wed Feb 18 17:24:38 2009 From: dsandras at seconix.com (Damien Sandras) Date: Wed, 18 Feb 2009 18:24:38 +0100 Subject: [Ekiga-list] ekiga timeout - eeebuntu In-Reply-To: References: Message-ID: <1234977878.11150.22.camel@scorpion.multitel.be> Le mercredi 18 f?vrier 2009 ? 00:13 +0300, Fedor vonBock a ?crit : > hi, > i'm trying to use ekiga on my new laptop (eee) but this registration > failed message always appears > > > i run ekiga -d 4 in the command prompt and here's the log from the > beginning up until it says registration timeout > > > > > > what do you think? It shows a 'symmetric NAT', please read our wiki at http://wiki.ekiga.org to know what to do when you have such a NAT scenario. -- _ 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 Feb 18 17:25:29 2009 From: dsandras at seconix.com (Damien Sandras) Date: Wed, 18 Feb 2009 18:25:29 +0100 Subject: [Ekiga-list] Ekiga 3.02 for Windows: Logitech QuickCam Pro9000 and choosing Default-SIP ? In-Reply-To: <499A531A.5040208@h-bauer.de> References: <4999220F.1000305@h-bauer.de> <499977D0.9050803@cchtml.com> <49997EE9.1070500@h-bauer.de> <499A531A.5040208@h-bauer.de> Message-ID: <1234977929.11150.24.camel@scorpion.multitel.be> Le mardi 17 f?vrier 2009 ? 07:03 +0100, Hans Bauer a ?crit : > > > Hans Bauer wrote: > > Michael Cronenworth wrote: > > > > > -------- Original Message -------- > > > Subject: [Ekiga-list] Ekiga 3.02 for Windows: Logitech QuickCam > > > Pro9000 and choosing Default-SIP ? > > > From: Hans Bauer > > > To: ekiga-list at gnome.org > > > Date: 02/16/2009 02:21 AM > > > > > > > > > > > > > Is there any possiblity to use my webcam with Ekiga 3.02 for Windows? > > > > > > > > > > > Microsoft WDM Image Capture is what you want. I, too, have a Logitech > > > QuickCam 9000. > > > > > > > > > > > > > > Michael, thank you. I already tried to choose Microsoft WDM Image > > Capture but got an access error stating that my video device already is > > used by another application, but it isn't. I previously shut down x-lite > > and even WinTV (Hauppauge). No other application on my pc is able to > > utilize video. After the statement is closed i'm also asked for > > sufficient rights for the video device "Microsoft WDM Image Capture" but > > i am already working as admin. Closing ekiga and opening the logitech > > webcam application shows that the webcam is working properly (all > > drivers installed). > > > Since today, after choosing Microsoft WDM Image Capture, my PC crashes > each time i start and activate Ekiga 3.02 for Windows. I had to > deinstall Ekiga. Sorry, but i will have to switch back to 2.0.11-beta > until 3.20 is out to try. > > Thanks for your support and my best wishes. > That means there is a bug in the WDM driver of your webcam. Try upgrading it. But I will ask if people contributing to the WIN32 build can also build our 'DirectVideo' capture plugin. It might work with 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 mike at cchtml.com Wed Feb 18 18:45:35 2009 From: mike at cchtml.com (Michael Cronenworth) Date: Wed, 18 Feb 2009 12:45:35 -0600 Subject: [Ekiga-list] Ekiga 3.02 for Windows: Logitech QuickCam Pro9000 and choosing Default-SIP ? In-Reply-To: <1234977929.11150.24.camel@scorpion.multitel.be> References: <4999220F.1000305@h-bauer.de> <499977D0.9050803@cchtml.com> <49997EE9.1070500@h-bauer.de> <499A531A.5040208@h-bauer.de> <1234977929.11150.24.camel@scorpion.multitel.be> Message-ID: <499C574F.5070904@cchtml.com> -------- Original Message -------- Subject: Re: [Ekiga-list] Ekiga 3.02 for Windows: Logitech QuickCam Pro9000 and choosing Default-SIP ? From: Damien Sandras To: hb at h-bauer.de, Ekiga mailing list Date: 02/18/2009 11:25 AM > Le mardi 17 f?vrier 2009 ? 07:03 +0100, Hans Bauer a ?crit : > > That means there is a bug in the WDM driver of your webcam. Try > upgrading it. > > But I will ask if people contributing to the WIN32 build can also build > our 'DirectVideo' capture plugin. It might work with it. Is that a separate library? Configure argument? I have DirectShow capture compiled in and the Preferences dialog only shows WDM capture. P.S. There is no update for the Logitech webcams in Windows. From mike at cchtml.com Wed Feb 18 18:48:49 2009 From: mike at cchtml.com (Michael Cronenworth) Date: Wed, 18 Feb 2009 12:48:49 -0600 Subject: [Ekiga-list] Trouble using Ekiga Win32 with Bonjour In-Reply-To: <5ca9a62d0902180812n7f213c46x3cd7551beb99fbf0@mail.gmail.com> References: <5ca9a62d0902180812n7f213c46x3cd7551beb99fbf0@mail.gmail.com> Message-ID: <499C5811.6070208@cchtml.com> -------- Original Message -------- Subject: [Ekiga-list] Trouble using Ekiga Win32 with Bonjour From: Epelde Gorka To: Ekiga mailing list Date: 02/18/2009 10:12 AM > Does this release include zeroconf functionalities? If not if there > any build of 3.0.2 for win32 with zeroconf support? I will have to see if zeroconf has a mingw compatible library. It'll be a few days. I'm trying to get back to Ekiga win32 stuff. From f.vonbock at gmail.com Wed Feb 18 19:31:25 2009 From: f.vonbock at gmail.com (Fedor vonBock) Date: Wed, 18 Feb 2009 22:31:25 +0300 Subject: [Ekiga-list] OpalUDP Error on connection read select Message-ID: hi, i tried to make a call on ekiga and i got this in the log whhen i used ekiga -d 1 tk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated 2009/02/18 22:28:30.032 0:02.190 ekiga Ekiga version 2.0.12 2009/02/18 22:28:30.034 0:02.192 ekiga OPAL version 2.2.11 2009/02/18 22:28:30.036 0:02.194 ekiga PWLIB version 1.10.10 2009/02/18 22:28:30.037 0:02.195 ekiga GNOME support enabled 2009/02/18 22:28:30.039 0:02.197 ekiga Fullscreen support enabled 2009/02/18 22:28:30.041 0:02.199 ekiga DBUS support enabled 2009/02/18 22:28:30.051 0:02.209 ekiga Set TCP port range to 30000:30010 2009/02/18 22:28:30.052 0:02.211 ekiga Set RTP port range to 5000:5059 2009/02/18 22:28:30.054 0:02.212 ekiga Set UDP port range to 5060:5100 2009/02/18 22:28:30.314 0:02.473 ekiga AVAHI Adding service Ali Khalfan 2009/02/18 22:28:31.170 0:03.328 ekiga AVAHI Adding service Ali Khalfan #2 2009/02/18 22:28:31.949 0:04.107 GMAccounts...t:09698700 SIP Created Transport for Registrar udp$86.64.162.35:5060 2009/02/18 22:28:32.270 0:04.429 GMAccounts...t:09698700 SIP Created Transport for Registrar udp$86.64.162.35:5060 2009/02/18 22:28:57.370 0:29.528 GMURLHandler:095a1000 SetUpCall succeeded 2009/02/18 22:28:58.346 0:30.505 SIP Transport:97c9950 OpalUDP Error on connection read select . -------------- next part -------------- An HTML attachment was scrubbed... URL: From f.vonbock at gmail.com Wed Feb 18 19:46:31 2009 From: f.vonbock at gmail.com (Fedor vonBock) Date: Wed, 18 Feb 2009 22:46:31 +0300 Subject: [Ekiga-list] ekiga timeout - eeebuntu In-Reply-To: <1234977878.11150.22.camel@scorpion.multitel.be> References: <1234977878.11150.22.camel@scorpion.multitel.be> Message-ID: thanks damien, it still times out now..but it seems to be a new thing now: what do you think 2009/02/18 22:44:29.630 0:08.657 Housekeeper SIP Transaction 2 SUBSCRIBE timeout, making retry 3 2009/02/18 22:44:29.632 0:08.659 Housekeeper SIP Sending PDU on udp$62.4.81.180:5060 SUBSCRIBE sip:324278 at eugw.ast.diamondcard.usSIP/2.0 CSeq: 2 SUBSCRIBE Via: SIP/2.0/UDP 89.148.38.109:5064 ;branch=z9hG4bK520ba037-62fc-dd11-96aa-0015afe7d424;rport User-Agent: Ekiga/2.0.12 From: >;tag=3e01a037-62fc-dd11-96aa-0015afe7d424 Call-ID: e46f7737-62fc-dd11-96aa-0015afe7d424 at khalfan-laptop To: > Contact: Accept: application/simple-message-summary Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Expires: 3600 Event: message-summary Content-Length: 0 Max-Forwards: 70 2009/02/18 22:44:30.006 0:09.033 Housekeeper SIP Transaction 3 REGISTER timeout, making retry 3 2009/02/18 22:44:30.007 0:09.034 Housekeeper SIP Sending PDU on udp$86.64.162.35:5060 REGISTER sip:ekiga.net SIP/2.0 CSeq: 3 REGISTER Via: SIP/2.0/UDP 89.148.38.109:5065 ;branch=z9hG4bKfe66d937-62fc-dd11-96aa-0015afe7d424;rport User-Agent: Ekiga/2.0.12 From: >;tag=525ed937-62fc-dd11-96aa-0015afe7d424 Call-ID: aa86a937-62fc-dd11-96aa-0015afe7d424 at khalfan-laptop To: > Contact: Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Expires: 3600 Content-Length: 0 Max-Forwards: 70 2009/02/18 22:44:31.426 0:10.453 Housekeeper SIP Transaction 4 SUBSCRIBE timeout, making retry 3 2009/02/18 22:44:31.428 0:10.455 Housekeeper SIP Sending PDU on udp$86.64.162.35:5060 SUBSCRIBE sip:alikhalfan1 at ekiga.net SIP/2.0 CSeq: 4 SUBSCRIBE Via: SIP/2.0/UDP 89.148.38.109:5066 ;branch=z9hG4bK68b5b138-62fc-dd11-96aa-0015afe7d424;rport User-Agent: Ekiga/2.0.12 From: >;tag=a0aab138-62fc-dd11-96aa-0015afe7d424 Call-ID: 02dae437-62fc-dd11-96aa-0015afe7d424 at khalfan-laptop To: > Contact: Accept: application/simple-message-summary Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Expires: 3600 Event: message-summary Content-Length: 0 Max-Forwards: 70 2009/02/18 22:44:31.822 0:10.849 Housekeeper SIP Set state Terminated_Timeout for transaction 1 REGISTER 2009/02/18 22:44:32.126 0:11.153 Housekeeper SIP Set state Terminated_Timeout for transaction 2 SUBSCRIBE 2009/02/18 22:44:32.498 0:11.525 Housekeeper SIP Set state Terminated_Timeout for transaction 3 REGISTER 2009/02/18 22:44:33.918 0:12.945 Housekeeper SIP Set state Terminated_Timeout for transaction 4 SUBSCRIBE ^CKilled khalfan at khalfan-laptop:~$ On Wed, Feb 18, 2009 at 8:24 PM, Damien Sandras wrote: > Le mercredi 18 f?vrier 2009 ? 00:13 +0300, Fedor vonBock a ?crit : > > hi, > > i'm trying to use ekiga on my new laptop (eee) but this registration > > failed message always appears > > > > > > i run ekiga -d 4 in the command prompt and here's the log from the > > beginning up until it says registration timeout > > > > > > > > > > > > what do you think? > > > It shows a 'symmetric NAT', please read our wiki at > http://wiki.ekiga.org to know what to do when you have such a NAT > scenario. > > -- > _ 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 mark.carey at gmail.com Wed Feb 18 20:24:07 2009 From: mark.carey at gmail.com (Mark Carey) Date: Thu, 19 Feb 2009 09:24:07 +1300 Subject: [Ekiga-list] Windows XP Quickcam Pro 9000 crashes Ekiga Message-ID: <34576580902181224i1e9ef5d9k6e92d549902db41c@mail.gmail.com> Hi, Have installed ekiga-setup-3.0.2-gtk-2.14.7.exe on Windows XP, using a Logitech Quickcam Pro 9000 webcam. When click on the "Display images from your camera device" button on the "Call Panel" Windows presents the "Video Source" dialog selecting "Logitech QuickCam Pro 9000" and pressing apply crashes windows hard and automatically reboots the machine. We can capture video fine from the camera in the same USB port etc using Windows Movie Maker, any suggestions, dxdiag says that everything is fine, any other tuning nobs we need to poke at? Regards, Mark Carey -------------- next part -------------- A non-text attachment was scrubbed... Name: video-source.png Type: image/png Size: 10867 bytes Desc: not available URL: From mark.carey at gmail.com Wed Feb 18 22:42:08 2009 From: mark.carey at gmail.com (Mark Carey) Date: Thu, 19 Feb 2009 11:42:08 +1300 Subject: [Ekiga-list] Windows XP Quickcam Pro 9000 crashes Windows Message-ID: <34576580902181442t7ab2bed2he5bb41e641b8af4b@mail.gmail.com> On Thu, Feb 19, 2009 at 9:24 AM, Mark Carey wrote: > Have installed ekiga-setup-3.0.2-gtk-2.14.7.exe on Windows XP, using a > Logitech Quickcam Pro 9000 webcam. > > When click on the "Display images from your camera device" button on > the "Call Panel" Windows presents the "Video Source" dialog selecting > "Logitech QuickCam Pro 9000" and pressing apply crashes windows hard > and automatically reboots the machine. > > We can capture video fine from the camera in the same USB port etc > using Windows Movie Maker, any suggestions, dxdiag says that > everything is fine, any other tuning nobs we need to poke at? After hitting send now see the thread titled "Ekiga 3.02 for Windows: Logitech QuickCam Pro9000 and choosing Default-SIP ?" not sure that the problem is the Logitech camera. Hans email dated "Tue, 17 Feb 2009 07:03:06 +0100" notes "...since today..." which suggests a change in behaviour. We appear to be having the same crashing behaviour with the QuickCam 9000 as Hans At our end I have now tested with; 1. Logitech QuickCam 9000 via USB crashes windows, displays video fine in Windows Movie Maker And additional camers additional cameras; 2. Fuji FinePix S5600 via ATI Radeon 9250 video capture (VIVO), displays video fine in Windows Movie Maker, no video displayed in Ekiga (at least doesnt crash windows!) 3. Fuji FinePix S5500 via USB (web mode), displays video fine in Windows Movie Maker, no video displayed in Ekiga (also doesnt crash windows) Hopefully additional data points that help localise the issue. Ekiga is great keep up the great work! Mark From ayresw at gmail.com Thu Feb 19 04:15:21 2009 From: ayresw at gmail.com (ayresw) Date: Wed, 18 Feb 2009 20:15:21 -0800 Subject: [Ekiga-list] Empty white pages Message-ID: <1235016921.6779.5.camel@localhost.localdomain> Hello, I'm new to Ekiga, and wondering why I can't get anything to appear in the 'Ekiga white pages' or 'contacts near me' sections of the address book. I'm running Ekiga 2.0.1 on mac osx 10.4 Thanks From ayresw at gmail.com Thu Feb 19 04:57:13 2009 From: ayresw at gmail.com (ayresw) Date: Wed, 18 Feb 2009 20:57:13 -0800 Subject: [Ekiga-list] Empty white pages In-Reply-To: <1235016921.6779.5.camel@localhost.localdomain> References: <1235016921.6779.5.camel@localhost.localdomain> Message-ID: <1235019433.5060.3.camel@localhost.localdomain> On Wed, 2009-02-18 at 20:15 -0800, ayresw wrote: > Hello, > > I'm new to Ekiga, and wondering why I can't get anything to appear in > the 'Ekiga white pages' or 'contacts near me' sections of the address > book. I'm running Ekiga 2.0.1 on mac osx 10.4 > > Thanks Correction! I'm running Ekiga 2.0.1 on Ubuntu 6.06 (2.6.15-53-386) From mtbc at ixod.org Thu Feb 19 05:32:47 2009 From: mtbc at ixod.org (Mark T.B. Carroll) Date: Thu, 19 Feb 2009 00:32:47 -0500 Subject: [Ekiga-list] Incoming call failure with 3.1.1 Message-ID: <87iqn7t2io.fsf@ixod.org> I have run through the configuration assistant thing from start to finish. I can call the 500 at ekiga.net echo test and that works just fine. However, calling the 520 at ekiga.net callback service has it hang up on me and then ... nothing, though the -d 5 output shows that it is indeed getting a callback initiated from from sip:500 at ekiga.net which is then aborted. I am behind NAT and the router forwards incoming UDP from port 5060 to 5100 to the machine I'm using and acts as a gateway to let all my outgoing packets out. Should I gzip my -d 4 output and send it to somebody? I can also sniff packets and send pcap files. I use Debian; software versions are, ekiga-snapshot 0-20090214-1 evolution-data-server 2.22.3-1.1 gconf2 2.24.0-6 libatk1.0-0 1.22.0-1 libavahi-client3 0.6.23-3lenny1 libavahi-common3 0.6.23-3lenny1 libavahi-glib1 0.6.23-3lenny1 libc6 2.7-18 libebook1.2-9 2.22.3-1.1 libedataserver1.2-9 2.22.3-1.1 libgcc1 1:4.3.2-1.1 libgconf2-4 2.24.0-6 libglib2.0-0 2.18.4-2 libgtk2.0-0 2.14.7-2 libldap-2.4-2 2.4.11-1 libnotify1 0.4.4-3 libopal-snapshot 0-20090214-1 libpango1.0-0 1.22.4-2 libpt-snapshot 0-20090214-1 libpt-snapshot-plugins-a 0-20090214-1 libpt-snapshot-plugins-v 0-20090214-1 libsasl2-2 2.1.22.dfsg1-23 libsigc++-2.0-0c2a 2.0.18-2 libstdc++6 4.3.2-1.1 libx11-6 2:1.1.5-2 libxext6 2:1.0.4-1 libxml2 2.6.32.dfsg-5 libxv1 2:1.0.4-1 (Incidentally, quitting from Ekiga seems to cause a segfault. I don't much mind that though.) It's entirely plausible that I'm simply doing something dumb, as I've never managed to get incoming calls working before. Thanks, Mark From jpuydt at free.fr Thu Feb 19 08:44:06 2009 From: jpuydt at free.fr (Julien Puydt) Date: Thu, 19 Feb 2009 09:44:06 +0100 Subject: [Ekiga-list] Empty white pages In-Reply-To: <1235019433.5060.3.camel@localhost.localdomain> References: <1235016921.6779.5.camel@localhost.localdomain> <1235019433.5060.3.camel@localhost.localdomain> Message-ID: <499D1BD6.7090101@free.fr> ayresw a ?crit : > Correction! I'm running Ekiga 2.0.1 on Ubuntu 6.06 (2.6.15-53-386) 2.0.1 !? Are you kidding!? We're up to version 3.0.2, and 2.0.1 was a very short-lived sub-version. Snark on #ekiga From dsandras at seconix.com Thu Feb 19 08:51:53 2009 From: dsandras at seconix.com (Damien Sandras) Date: Thu, 19 Feb 2009 09:51:53 +0100 Subject: [Ekiga-list] Empty white pages In-Reply-To: <1235016921.6779.5.camel@localhost.localdomain> References: <1235016921.6779.5.camel@localhost.localdomain> Message-ID: <1235033513.4022.3.camel@scorpion.multitel.be> Le mercredi 18 f?vrier 2009 ? 20:15 -0800, ayresw a ?crit : > Hello, > > I'm new to Ekiga, and wondering why I can't get anything to appear in > the 'Ekiga white pages' or 'contacts near me' sections of the address > book. I'm running Ekiga 2.0.1 on mac osx 10.4 The service was crashed. -- _ 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 hoogland at gmail.com Thu Feb 19 14:19:49 2009 From: hoogland at gmail.com (Jason Hoogland) Date: Fri, 20 Feb 2009 00:19:49 +1000 Subject: [Ekiga-list] Data transfer statistics Message-ID: Hi, Ekiga provides call duration for past calls, how can you get associated data transfer volumes? Jason From leamas.alec at gmail.com Thu Feb 19 14:59:00 2009 From: leamas.alec at gmail.com (Alec Leamas) Date: Thu, 19 Feb 2009 15:59:00 +0100 Subject: [Ekiga-list] Resolved: Thompson ST585 v6 router stability problems In-Reply-To: References: Message-ID: <499D73B4.4020602@gmail.com> I have the the subject router, a decision from my ISP I have to live with. I've really never been able achieve long-term stability with Ekiga, the registration has dropped after some time (~1 hour?). Another strange symptom has been the Edit Acoount Dialog. When invoked and saved with the same data, my registrar became "Unregistered". Repeating the Edit/Save procedure, still w same data, turned the registrar to "Registered". To make it work at all I after a while found out that the router has an Application Layer Gateway (ALG) for sip (thanks, Damien!). Using this means to disable stun, and rely on the the routers' sip management. And indeed, I could both call place and recieve calls. But no long-term stability. The problem seems to be the ALG, it's just buggy according to a lot of threads out there. Furhermore, it cannot be disabled with the v6 version of the firmware. It was possible in some older versions(!) Solution: go around the ALG by using another port than 5060 (I use 5080). Enable stun. Setup port forwarding (a k a Game Sharing...) to port 5080/UDP in the router. Done. BTW: this means that it's not a trivial setup decision to use the ALG just because it's there. This ? propos the discussion about automatic recognition of sip-aware routers in the initial configuration wizard. Cheers --alec From ayresw at gmail.com Thu Feb 19 15:08:22 2009 From: ayresw at gmail.com (ayresw) Date: Thu, 19 Feb 2009 07:08:22 -0800 Subject: [Ekiga-list] Empty white pages In-Reply-To: <499D1BD6.7090101@free.fr> References: <1235016921.6779.5.camel@localhost.localdomain> <1235019433.5060.3.camel@localhost.localdomain> <499D1BD6.7090101@free.fr> Message-ID: <1235056103.5158.3.camel@localhost.localdomain> I checked the Ubuntu package list. All versions use 2.0.x except jaunty, which. On Thu, 2009-02-19 at 09:44 +0100, Julien Puydt wrote: > ayresw a ?crit : > > Correction! I'm running Ekiga 2.0.1 on Ubuntu 6.06 (2.6.15-53-386) > > 2.0.1 !? Are you kidding!? We're up to version 3.0.2, and 2.0.1 was a > very short-lived sub-version. > > Snark on #ekiga > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list I checked the Ubuntu package list. All versions use 2.0.x except jaunty, which is 3.01. Perhaps I'll re-install manually. From ayresw at gmail.com Thu Feb 19 15:09:19 2009 From: ayresw at gmail.com (ayresw) Date: Thu, 19 Feb 2009 07:09:19 -0800 Subject: [Ekiga-list] Empty white pages In-Reply-To: <1235033513.4022.3.camel@scorpion.multitel.be> References: <1235016921.6779.5.camel@localhost.localdomain> <1235033513.4022.3.camel@scorpion.multitel.be> Message-ID: <1235056159.5158.4.camel@localhost.localdomain> On Thu, 2009-02-19 at 09:51 +0100, Damien Sandras wrote: > Le mercredi 18 f?vrier 2009 ? 20:15 -0800, ayresw a ?crit : > > Hello, > > > > I'm new to Ekiga, and wondering why I can't get anything to appear in > > the 'Ekiga white pages' or 'contacts near me' sections of the address > > book. I'm running Ekiga 2.0.1 on mac osx 10.4 > > The service was crashed. > -- Thank you, Its working now. From mtbc at ixod.org Thu Feb 19 15:33:07 2009 From: mtbc at ixod.org (Mark T.B. Carroll) Date: Thu, 19 Feb 2009 10:33:07 -0500 Subject: [Ekiga-list] ekiga-snapshot-config-tool Debian packaging looks for wrong schema file Message-ID: <87ocwyqw5o.fsf@ixod.org> ekiga-snapshot-config-tool --install-schemas gives, I/O warning : failed to load external entity "/etc/gconf/schemas/ekiga.schemas" Failed to open `/etc/gconf/schemas/ekiga.schemas': No such file or directory My version of the ekiga-snapshot Debian package is 0-20090214-1 which instead has a /usr/share/gconf/schemas/ekiga-snapshot.schemas file. Mark From dsandras at seconix.com Thu Feb 19 16:55:42 2009 From: dsandras at seconix.com (Damien Sandras) Date: Thu, 19 Feb 2009 17:55:42 +0100 Subject: [Ekiga-list] ekiga timeout - eeebuntu In-Reply-To: References: <1234977878.11150.22.camel@scorpion.multitel.be> Message-ID: <1235062542.23177.4.camel@scorpion.multitel.be> Le mercredi 18 f?vrier 2009 ? 22:46 +0300, Fedor vonBock a ?crit : > thanks damien, > > > it still times out now..but it seems to be a new thing now: what do > you think I don't see the problem as being different. Does it still detect symmetric nat 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 Thu Feb 19 16:57:09 2009 From: dsandras at seconix.com (Damien Sandras) Date: Thu, 19 Feb 2009 17:57:09 +0100 Subject: [Ekiga-list] Windows XP Quickcam Pro 9000 crashes Windows In-Reply-To: <34576580902181442t7ab2bed2he5bb41e641b8af4b@mail.gmail.com> References: <34576580902181442t7ab2bed2he5bb41e641b8af4b@mail.gmail.com> Message-ID: <1235062629.23177.6.camel@scorpion.multitel.be> Le jeudi 19 f?vrier 2009 ? 11:42 +1300, Mark Carey a ?crit : > On Thu, Feb 19, 2009 at 9:24 AM, Mark Carey wrote: > > Have installed ekiga-setup-3.0.2-gtk-2.14.7.exe on Windows XP, using a > > Logitech Quickcam Pro 9000 webcam. > > > > When click on the "Display images from your camera device" button on > > the "Call Panel" Windows presents the "Video Source" dialog selecting > > "Logitech QuickCam Pro 9000" and pressing apply crashes windows hard > > and automatically reboots the machine. > > > > We can capture video fine from the camera in the same USB port etc > > using Windows Movie Maker, any suggestions, dxdiag says that > > everything is fine, any other tuning nobs we need to poke at? > > After hitting send now see the thread titled "Ekiga 3.02 for Windows: > Logitech QuickCam Pro9000 and choosing Default-SIP ?" not sure that > the problem is the Logitech camera. Hans email dated "Tue, 17 Feb > 2009 07:03:06 +0100" notes "...since today..." which suggests a change > in behaviour. > > We appear to be having the same crashing behaviour with the QuickCam > 9000 as Hans > > At our end I have now tested with; > > 1. Logitech QuickCam 9000 via USB crashes windows, displays video fine > in Windows Movie Maker > > And additional camers additional cameras; > > 2. Fuji FinePix S5600 via ATI Radeon 9250 video capture (VIVO), > displays video fine in Windows Movie Maker, no video displayed in > Ekiga (at least doesnt crash windows!) > > 3. Fuji FinePix S5500 via USB (web mode), displays video fine in > Windows Movie Maker, no video displayed in Ekiga (also doesnt crash > windows) > > Hopefully additional data points that help localise the issue. > If it crashes Windows, then it is a windows problem. We have relatively few latitude to fix that. However, new packs with DirectVideo support will be built, you might want to try them out and see if the directvideo plugin also crashes Windows 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 Thu Feb 19 16:57:30 2009 From: dsandras at seconix.com (Damien Sandras) Date: Thu, 19 Feb 2009 17:57:30 +0100 Subject: [Ekiga-list] Incoming call failure with 3.1.1 In-Reply-To: <87iqn7t2io.fsf@ixod.org> References: <87iqn7t2io.fsf@ixod.org> Message-ID: <1235062650.23177.8.camel@scorpion.multitel.be> Le jeudi 19 f?vrier 2009 ? 00:32 -0500, Mark T.B. Carroll a ?crit : > I have run through the configuration assistant thing from start to > finish. I can call the 500 at ekiga.net echo test and that works just fine. > However, calling the 520 at ekiga.net callback service has it hang up on me > and then ... nothing, though the -d 5 output shows that it is indeed > getting a callback initiated from from sip:500 at ekiga.net which is then > aborted. I am behind NAT and the router forwards incoming UDP from port > 5060 to 5100 to the machine I'm using and acts as a gateway to let all > my outgoing packets out. > > Should I gzip my -d 4 output and send it to somebody? I can also sniff > packets and send pcap files. I use Debian; software versions are, > There is a known problem with incoming calls and the current snapshot. I will 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 dsandras at seconix.com Thu Feb 19 16:57:39 2009 From: dsandras at seconix.com (Damien Sandras) Date: Thu, 19 Feb 2009 17:57:39 +0100 Subject: [Ekiga-list] Data transfer statistics In-Reply-To: References: Message-ID: <1235062659.23177.10.camel@scorpion.multitel.be> Le vendredi 20 f?vrier 2009 ? 00:19 +1000, Jason Hoogland a ?crit : > Hi, > > Ekiga provides call duration for past calls, how can you get > associated data transfer volumes? > It's not possible. -- _ 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 Feb 19 16:58:09 2009 From: dsandras at seconix.com (Damien Sandras) Date: Thu, 19 Feb 2009 17:58:09 +0100 Subject: [Ekiga-list] Resolved: Thompson ST585 v6 router stability problems In-Reply-To: <499D73B4.4020602@gmail.com> References: <499D73B4.4020602@gmail.com> Message-ID: <1235062689.23177.12.camel@scorpion.multitel.be> Le jeudi 19 f?vrier 2009 ? 15:59 +0100, Alec Leamas a ?crit : > I have the the subject router, a decision from my ISP I have to live > with. I've really never been able achieve long-term stability with > Ekiga, the registration has dropped after some time (~1 hour?). Another > strange symptom has been the Edit Acoount Dialog. When invoked and saved > with the same data, my registrar became "Unregistered". Repeating the > Edit/Save procedure, still w same data, turned the registrar to > "Registered". > > To make it work at all I after a while found out that the router has an > Application Layer Gateway (ALG) for sip (thanks, Damien!). Using this > means to disable stun, and rely on the the routers' sip management. And > indeed, I could both call place and recieve calls. But no long-term > stability. > > The problem seems to be the ALG, it's just buggy according to a lot of > threads out there. Furhermore, it cannot be disabled with the v6 version > of the firmware. It was possible in some older versions(!) > > Solution: go around the ALG by using another port than 5060 (I use > 5080). Enable stun. Setup port forwarding (a k a Game Sharing...) to > port 5080/UDP in the router. Done. > > BTW: this means that it's not a trivial setup decision to use the ALG > just because it's there. This ? propos the discussion about automatic > recognition of sip-aware routers in the initial configuration wizard. Thanks for the feedback! Please report them a bug... -- _ 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 Feb 19 16:58:46 2009 From: dsandras at seconix.com (Damien Sandras) Date: Thu, 19 Feb 2009 17:58:46 +0100 Subject: [Ekiga-list] Ekiga 3.02 for Windows: Logitech QuickCam Pro9000 and choosing Default-SIP ? In-Reply-To: <499C574F.5070904@cchtml.com> References: <4999220F.1000305@h-bauer.de> <499977D0.9050803@cchtml.com> <49997EE9.1070500@h-bauer.de> <499A531A.5040208@h-bauer.de> <1234977929.11150.24.camel@scorpion.multitel.be> <499C574F.5070904@cchtml.com> Message-ID: <1235062726.23177.14.camel@scorpion.multitel.be> Le mercredi 18 f?vrier 2009 ? 12:45 -0600, Michael Cronenworth a ?crit : > -------- Original Message -------- > Subject: Re: [Ekiga-list] Ekiga 3.02 for Windows: Logitech QuickCam > Pro9000 and choosing Default-SIP ? > From: Damien Sandras > To: hb at h-bauer.de, Ekiga mailing list > Date: 02/18/2009 11:25 AM > > > Le mardi 17 f?vrier 2009 ? 07:03 +0100, Hans Bauer a ?crit : > > > > That means there is a bug in the WDM driver of your webcam. Try > > upgrading it. > > > > But I will ask if people contributing to the WIN32 build can also build > > our 'DirectVideo' capture plugin. It might work with it. > > > Is that a separate library? Configure argument? I have DirectShow > capture compiled in and the Preferences dialog only shows WDM capture. There is probably a reason why it does not load in that case. Probably a compilation flag. -- _ 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 mark.carey at gmail.com Fri Feb 20 03:24:03 2009 From: mark.carey at gmail.com (Mark Carey) Date: Fri, 20 Feb 2009 16:24:03 +1300 Subject: [Ekiga-list] Windows XP Quickcam Pro 9000 crashes Windows Message-ID: <34576580902191924y6c1cf83ega6fc882be8432638@mail.gmail.com> > If it crashes Windows, then it is a windows problem. We have relatively > few latitude to fix that. However, new packs with DirectVideo support > will be built, you might want to try them out and see if the directvideo > plugin also crashes Windows or not. Damien, Agree entirely that if it is a Windows problem then there is nothing Ekiga folks can do about it. Also I clearly dont understand enough about Windows and its many software layers for video etc, e.g where does that "video source" dialog come from it looks like something out of win95 following the transition from win 3.11, how does one get to the dialog to show? Where does that dialog save it settings and which windows component has to be reinstalled to reinitialise it. Video on Windows is starting to appear much more like the maze of ffmpeg + gstreamer + uvcvideo + ...... on a *nix box. It does strike me as strange that when Ekiga fires the hardware up Windows crashes and it works normally with non ekiga apps, it is possible that ekiga is using a different code paths to all other Windows apps we have tested, it is possible that there is a bug in a windows API that nothing else that I have tested exposes. And raises an interesting philosophical observation, as more and more foss apps find their way into windows it is going to expose more and more the fragile points of Windows support, WDM, etc. Tried an alternative route got Ubuntu 8.10 installed on another machine, only to find Canonical bundled ekiga 2.0.11 and offered no backport of 3.0.2, built 3.0.2 from source only to hit some variant of the "pulseaudio and ekiga do not play nice bug" Thanks for the heads up, look forward to a win32 build with a directvideo plugin for testing, keep up the great work. Regards, Mark Carey From f.vonbock at gmail.com Fri Feb 20 06:47:27 2009 From: f.vonbock at gmail.com (Fedor vonBock) Date: Fri, 20 Feb 2009 09:47:27 +0300 Subject: [Ekiga-list] ekiga timeout - eeebuntu In-Reply-To: <1235062542.23177.4.camel@scorpion.multitel.be> References: <1234977878.11150.22.camel@scorpion.multitel.be> <1235062542.23177.4.camel@scorpion.multitel.be> Message-ID: now it says stun detects cone nat when i press detect nat type On Thu, Feb 19, 2009 at 7:55 PM, Damien Sandras wrote: > Le mercredi 18 f?vrier 2009 ? 22:46 +0300, Fedor vonBock a ?crit : > > thanks damien, > > > > > > it still times out now..but it seems to be a new thing now: what do > > you think > > > I don't see the problem as being different. Does it still detect symmetric > nat 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 > > > _______________________________________________ > 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 Fri Feb 20 07:06:11 2009 From: dsandras at seconix.com (Damien Sandras) Date: Fri, 20 Feb 2009 08:06:11 +0100 Subject: [Ekiga-list] ekiga timeout - eeebuntu In-Reply-To: References: <1234977878.11150.22.camel@scorpion.multitel.be> <1235062542.23177.4.camel@scorpion.multitel.be> Message-ID: <1235113571.4044.0.camel@scorpion.multitel.be> Le vendredi 20 f?vrier 2009 ? 09:47 +0300, Fedor vonBock a ?crit : > now it says stun detects cone nat when i press detect nat type > Please provide a full log 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 steig at cs.stanford.edu Fri Feb 20 14:21:15 2009 From: steig at cs.stanford.edu (Menasheh Steiglitz) Date: Fri, 20 Feb 2009 16:21:15 +0200 Subject: [Ekiga-list] Logitech cameras for use with Ekiga for Windows? Message-ID: <24F319FB-5575-4EFF-9BBE-1A1943A4E39A@cs.stanford.edu> Are any of the currently available Logitech cameras (list follows) known to work with the current version of Ekiga for Windows? (I've seen the list on the wiki; perhaps someone has more recent experience since that list was compiled.) QuickCam E 2500 QuickCam E 3500 QuickCam Connect QuickCam for Notebooks QuickCam E 3500 Plus QuickCam S 5500 QuickCam Deluxe for Notebboks QuickCam S 7500 QuickCam Communicate STX QuickCam Communicate MP QuickCam Communicate Deluxe QuickCam Pro for Notebooks QuickCam Pro 9000 QuickCam Sphere AF QuickCam Orbit AF QuickCam Vision Pro From razametal at gmail.com Fri Feb 20 14:42:21 2009 From: razametal at gmail.com (RazaMetaL | Only The Good Die Young) Date: Fri, 20 Feb 2009 09:42:21 -0500 Subject: [Ekiga-list] Logitech cameras for use with Ekiga for Windows? In-Reply-To: <24F319FB-5575-4EFF-9BBE-1A1943A4E39A@cs.stanford.edu> References: <24F319FB-5575-4EFF-9BBE-1A1943A4E39A@cs.stanford.edu> Message-ID: On Fri, Feb 20, 2009 at 9:21 AM, Menasheh Steiglitz wrote: > Are any of the currently available Logitech cameras (list follows) known to > work with the current version of Ekiga for Windows? (I've seen the list on > the wiki; perhaps someone has more recent experience since that list was > compiled.) > > QuickCam E 2500 > QuickCam E 3500 > QuickCam Connect > QuickCam for Notebooks > QuickCam E 3500 Plus > QuickCam S 5500 > QuickCam Deluxe for Notebboks > QuickCam S 7500 > QuickCam Communicate STX > QuickCam Communicate MP > QuickCam Communicate Deluxe > QuickCam Pro for Notebooks > QuickCam Pro 9000 > QuickCam Sphere AF > QuickCam Orbit AF > QuickCam Vision Pro > Logitech QuickCam Pro 4000 Regards, -- Linux User: 255902 Please avoid sending me Word or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html From leamas.alec at gmail.com Sat Feb 21 15:57:59 2009 From: leamas.alec at gmail.com (Alec Leamas) Date: Sat, 21 Feb 2009 16:57:59 +0100 Subject: [Ekiga-list] Hacking: ekiga-callto update (last for a while...) Message-ID: <49A02487.2060509@gmail.com> There is yet another version of ekiga-callto. From the changelog: * Sat Feb 21 2009 Alec Leamas 0.2.19-1 - From my perspective: feature complete. - New homepage: http://mumin.dnsalias.net/ekiga-callto.html - New default configuration based on country as looked up from IP address. - New mini application for cut & paste numbers in documents, email etc. - Further improved number recognition - Got rid of the 'find-dist' installation kludge rpm. The major things is the web page (screenshots, at last!) and the new dial clipboard. Would be nice with a link from ekiga.org... I don't plan any more work with this for the moment. Cheers, --alec From leamas.alec at gmail.com Sat Feb 21 16:27:27 2009 From: leamas.alec at gmail.com (Alec Leamas) Date: Sat, 21 Feb 2009 17:27:27 +0100 Subject: [Ekiga-list] Handling of old-fashioned phone numbers Message-ID: <49A02B6F.9020308@gmail.com> Basically, I think this should not reside in a frontend like ekiga-callto, which is more like a prototype. There are some good reasons to integrate into the core application: - To make this functionality available also on Windows it's propably much better to have it in Ekiga. A dependency on gtk-python is actually not that nice in this environment (as opposed to Linux, where it's readily available from repos). - Integrating it into Ekiga should make it possible to use the same logic for numbers stored in PIM databases (e. g., Evolution) which typically lacks countrycode. ( see http://wiki.ekiga.org/index.php/API::GmContact::PhoneNumbers) - Configuration becomes easier when the list of available accounts is could be accessed. - The many steps and windows used by frontend + Ekiga is, taken together, not a really nice UI. To integrate it into current UI should give a much better user experience. The ability to handle the everyday numbers we have around us is actually crucial for everyday use. This is an area where Skype shines. So should also Ekiga! The najor drawback as I see it is to introduce still more configuration, based on the idea that numbers should be expanded in a country-based context. On the other hand default values could be provided which should be fine for almost all users. And the idea that numbers are local to a country is intuitive and should not pose a problem for users. And, of course, there is work. But having a prototype is a start. I see most of the difficulties in modifying the UI. Actually, I havn't any real ideas about this... From mariofutire at googlemail.com Sat Feb 21 18:29:17 2009 From: mariofutire at googlemail.com (Andrea) Date: Sat, 21 Feb 2009 18:29:17 +0000 Subject: [Ekiga-list] A comparison ALSA-PULSE Message-ID: Hi, I've tried to compare the behaviour of ALSA when Ekiga uses the direct access vs going through pulse-alsa module. I've added some alsa print status in ptlib and the 2 files are the output when playing the ring-tone. I've used the 2 alsa calls to populate the log 1) snd_pcm_dump at the beginning 2) snd_pcm_status_dump after each write The first part is the same, but the status after each write is different DIRECT About to write 1764 len bytes state : RUNNING trigger_time: 9762.542972003 <<<<<<<<<<<<<<<<<<<<<<<< tstamp : 9762.543004130 <<<<<<<<<<<<<<<<<<<<<<<< delay : 430 <<<<<<<<<<<<<<<<<<<<<<< avail : 1334 avail_max : 1334 PULSE About to write 1764 len bytes state : RUNNING trigger_time: 1235218239.552437000 <<<<<<<<<<<<<<< tstamp : 0.000000 <<<<<<<<<<<<<<< delay : 0 <<<<<<<<<<<<<<< avail : 441 avail_max : 1764 And then every now and then when running via pulse we generate an underrun About to write 1764 len bytes state : RUNNING trigger_time: 1235218239.552437000 tstamp : 0.000000 delay : 0 avail : 0 avail_max : 1764 ####################################################################### EPIPE state : XRUN trigger_time: 1235218239.552437000 tstamp : 0.000000 delay : 0 avail : 0 avail_max : 1764 Does anybody know a bit what all those values mean? It seems that the underrun comes earlier that without pulse-alsa... I've tried to increase the size of the buffers in PSoundChannelALSA::SetBuffers() and the playback is much better, but that gives a bigger latency and delay when calling the echo test. -------------- next part -------------- A non-text attachment was scrubbed... Name: status.direct.txt.gz Type: application/x-gzip Size: 2170 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: status.pulse.txt.gz Type: application/x-gzip Size: 1389 bytes Desc: not available URL: From mikhail.kalkov at gmail.com Sun Feb 22 08:32:56 2009 From: mikhail.kalkov at gmail.com (Mikhail Kalkov) Date: Sun, 22 Feb 2009 10:32:56 +0200 Subject: [Ekiga-list] ekiga -d 5: "Transaction REGISTER timeout" Message-ID: <9d6795d00902220032w5575db97hd091bed1df7b161@mail.gmail.com> Hi, all! I've just installed Ekiga 3.0.2 from sources at http://wiki.ekiga.org/index.php/Download_Ekiga_sources, and registered at Ekiga.net web site, but cannot get connected to the SIP server at ekiga.net. The status line tells me "Couldn't register to sip:myaddress at ekiga.net". According to 'ekiga -d 5' command output, it is trying to connect, but every time registration attempts time out. The interesting part starts when I try to troubleshoot it with Wireshark. It seems that the client actually sends the REGISTER message, and the server replies to it with a nonce and authorization request as it should, but the reply is sent to a random port in the range 15000-17000, whereas ekiga listens on port 5060. Obviously, the reply is discarded by the kernel, and it never reaches the destination. I am running Ubuntu 8.04, and tried to connect through my home switch as well as directly to the wall outlet. The ISP provides me with a public IP address, but filters incoming traffic, and although 'ekiga -d 5' reports a symmetric firewall, I have never noticed any filtering on the outgoing traffic. It's the first time for me to try Ekiga, or any voice messenger apart from Skype, and I may very well be wrong in some assumptions, but there were couple more similar reports in the mail list: * http://mail.gnome.org/archives/ekiga-list/2009-February/msg00170.html "[Ekiga-list] ekiga timeout - eeebuntu" * http://mail.gnome.org/archives/ekiga-list/2009-February/msg00120.html "[Ekiga-list] SIP server ekiga.org down?" * http://mail.gnome.org/archives/ekiga-list/2009-February/msg00098.html "[Ekiga-list] Fedora Core 10 - Ekiga 3.0.2 registration timeout()" Regards, Mikhail Kalkov -- () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments From dsandras at seconix.com Sun Feb 22 09:22:36 2009 From: dsandras at seconix.com (Damien Sandras) Date: Sun, 22 Feb 2009 10:22:36 +0100 Subject: [Ekiga-list] Handling of old-fashioned phone numbers In-Reply-To: <49A02B6F.9020308@gmail.com> References: <49A02B6F.9020308@gmail.com> Message-ID: <1235294556.3960.1.camel@scorpion.multitel.be> Hi, I think you did a great job. Comments inside. Le samedi 21 f?vrier 2009 ? 17:27 +0100, Alec Leamas a ?crit : > Basically, I think this should not reside in a frontend like > ekiga-callto, which is more like a prototype. There are some good > reasons to integrate into the core application: > > - To make this functionality available also on Windows it's propably > much better to have it in Ekiga. A dependency on gtk-python is actually > not that nice in this environment (as opposed to Linux, where it's > readily available from repos). > - Integrating it into Ekiga should make it possible to use the same > logic for numbers stored in PIM databases (e. g., Evolution) which > typically lacks countrycode. ( see > http://wiki.ekiga.org/index.php/API::GmContact::PhoneNumbers) > - Configuration becomes easier when the list of available accounts is > could be accessed. > - The many steps and windows used by frontend + Ekiga is, taken > together, not a really nice UI. To integrate it into current UI should > give a much better user experience. > > The ability to handle the everyday numbers we have around us is actually > crucial for everyday use. This is an area where Skype shines. So should > also Ekiga! > > The najor drawback as I see it is to introduce still more configuration, > based on the idea that numbers should be expanded in a country-based > context. On the other hand default values could be provided which should > be fine for almost all users. And the idea that numbers are local to a > country is intuitive and should not pose a problem for users. > > And, of course, there is work. But having a prototype is a start. I see > most of the difficulties in modifying the UI. Actually, I havn't any > real ideas about this... If you do the back-end (as you have the most experience), we can do the GUI (for Ekiga 3.4). Does that sound like a good idea for you? -- _ 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 Feb 22 09:23:43 2009 From: dsandras at seconix.com (Damien Sandras) Date: Sun, 22 Feb 2009 10:23:43 +0100 Subject: [Ekiga-list] A comparison ALSA-PULSE In-Reply-To: References: Message-ID: <1235294623.3960.3.camel@scorpion.multitel.be> Le samedi 21 f?vrier 2009 ? 18:29 +0000, Andrea a ?crit : > Hi, > > I've tried to compare the behaviour of ALSA when Ekiga uses the direct access vs going through > pulse-alsa module. > > I've added some alsa print status in ptlib and the 2 files are the output when playing the ring-tone. > > I've used the 2 alsa calls to populate the log > > 1) snd_pcm_dump at the beginning > 2) snd_pcm_status_dump after each write > > The first part is the same, but the status after each write is different > > DIRECT > > About to write 1764 len bytes > state : RUNNING > trigger_time: 9762.542972003 <<<<<<<<<<<<<<<<<<<<<<<< > tstamp : 9762.543004130 <<<<<<<<<<<<<<<<<<<<<<<< > delay : 430 <<<<<<<<<<<<<<<<<<<<<<< > avail : 1334 > avail_max : 1334 > > PULSE > > About to write 1764 len bytes > state : RUNNING > trigger_time: 1235218239.552437000 <<<<<<<<<<<<<<< > tstamp : 0.000000 <<<<<<<<<<<<<<< > delay : 0 <<<<<<<<<<<<<<< > avail : 441 > avail_max : 1764 > > > And then every now and then when running via pulse we generate an underrun > > About to write 1764 len bytes > state : RUNNING > trigger_time: 1235218239.552437000 > tstamp : 0.000000 > delay : 0 > avail : 0 > avail_max : 1764 > ####################################################################### EPIPE > state : XRUN > trigger_time: 1235218239.552437000 > tstamp : 0.000000 > delay : 0 > avail : 0 > avail_max : 1764 > > > Does anybody know a bit what all those values mean? > It seems that the underrun comes earlier that without pulse-alsa... > > I've tried to increase the size of the buffers in PSoundChannelALSA::SetBuffers() and the playback > is much better, but that gives a bigger latency and delay when calling the echo test. The pulseaudio guy told us we have a problem with the way we calculate the periods. Not sure exactly what is wrong though... -- _ 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 Feb 22 09:27:00 2009 From: dsandras at seconix.com (Damien Sandras) Date: Sun, 22 Feb 2009 10:27:00 +0100 Subject: [Ekiga-list] ekiga -d 5: "Transaction REGISTER timeout" In-Reply-To: <9d6795d00902220032w5575db97hd091bed1df7b161@mail.gmail.com> References: <9d6795d00902220032w5575db97hd091bed1df7b161@mail.gmail.com> Message-ID: <1235294820.3960.8.camel@scorpion.multitel.be> Le dimanche 22 f?vrier 2009 ? 10:32 +0200, Mikhail Kalkov a ?crit : > Hi, all! > > I've just installed Ekiga 3.0.2 from sources at > http://wiki.ekiga.org/index.php/Download_Ekiga_sources, and registered > at Ekiga.net web site, but cannot get connected to the SIP server at > ekiga.net. > > The status line tells me "Couldn't register to > sip:myaddress at ekiga.net". According to 'ekiga -d 5' command output, it > is trying to connect, but every time registration attempts time out. > The interesting part starts when I try to troubleshoot it with > Wireshark. It seems that the client actually sends the REGISTER > message, and the server replies to it with a nonce and authorization > request as it should, but the reply is sent to a random port in the > range 15000-17000, whereas ekiga listens on port 5060. Obviously, the > reply is discarded by the kernel, and it never reaches the > destination. > > I am running Ubuntu 8.04, and tried to connect through my home switch > as well as directly to the wall outlet. The ISP provides me with a > public IP address, but filters incoming traffic, and although 'ekiga > -d 5' reports a symmetric firewall, I have never noticed any filtering > on the outgoing traffic. The port is the port that is detected using the STUN test. STUN is there to determine what port the gateway will use for your traffic. It can not be 5060, because if it was 5060, then you could only have one SIP client running at a time in your private network. If the NAT is symmetric, it is impossible to guess the port that will be used on the router. -- _ 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 Feb 22 09:48:10 2009 From: leamas.alec at gmail.com (Alec Leamas) Date: Sun, 22 Feb 2009 10:48:10 +0100 Subject: [Ekiga-list] A comparison ALSA-PULSE In-Reply-To: References: Message-ID: <49A11F5A.7090908@gmail.com> Just some thoughts. Maybe it can provoke someone who knows better... If we had a pointer to cress-referenced code of the *dump routines we would be on much safer ground. It would be interesting to know the basic characteristics: sample rate, frame size, samplesize, period size...I remember something like cat /proc/asound/card0/pcm0p/sub0/hw_params, cat /proc/asound/card0/pcm0c/sub0/sw_params to get this info. I interpret delay as the time the calling routine has to sit waiting until there is space enough in the hardware buffer to write. Available reflects the numbers of (bytes? frames? samples?) available in the hw buffer for the sound card? Available_max: isn't this just the size of the hw buffer, in something( bytes? frames? samples?) i. e., the max number of entities which could be buffered? Isn't "trigger time" the time between each interrupt, basically the thing you are waiting for in snd_pcm_wait()? Is pulseaudio running with high nice value? Is the RTP jitter buffer a separate buffer, or is it using the alsa buffer for this purpose? Separate playback buffers is a major drawback, they add latency without being available to avoid underruns. Maybe it's possible to increase the alsa buffer and decrease the RTP playback buffer? Same latency, but less chance of underrun... There are real-world examples of hw buffers ~3600 bytes, with very acceptable latency (i. e., twice the buffer size here). But then that's the only buffers.... and it depends on samplerate etc. Alsa underruns behaves very differently depending on the calling routines. I don't know whether pulse handles underruns internally (they should!), or if it's a requirement for client code. Is this sorted out? Skype runs fine with pulseaudio drivers, so it's definitely possible... Andrea wrote: > Hi, > > I've tried to compare the behaviour of ALSA when Ekiga uses the direct access vs going through > pulse-alsa module. > > I've added some alsa print status in ptlib and the 2 files are the output when playing the ring-tone. > > I've used the 2 alsa calls to populate the log > > 1) snd_pcm_dump at the beginning > 2) snd_pcm_status_dump after each write > > The first part is the same, but the status after each write is different > > DIRECT > > About to write 1764 len bytes > state : RUNNING > trigger_time: 9762.542972003 <<<<<<<<<<<<<<<<<<<<<<<< > tstamp : 9762.543004130 <<<<<<<<<<<<<<<<<<<<<<<< > delay : 430 <<<<<<<<<<<<<<<<<<<<<<< > avail : 1334 > avail_max : 1334 > > PULSE > > About to write 1764 len bytes > state : RUNNING > trigger_time: 1235218239.552437000 <<<<<<<<<<<<<<< > tstamp : 0.000000 <<<<<<<<<<<<<<< > delay : 0 <<<<<<<<<<<<<<< > avail : 441 > avail_max : 1764 > > > And then every now and then when running via pulse we generate an underrun > > About to write 1764 len bytes > state : RUNNING > trigger_time: 1235218239.552437000 > tstamp : 0.000000 > delay : 0 > avail : 0 > avail_max : 1764 > ####################################################################### EPIPE > state : XRUN > trigger_time: 1235218239.552437000 > tstamp : 0.000000 > delay : 0 > avail : 0 > avail_max : 1764 > > > Does anybody know a bit what all those values mean? > It seems that the underrun comes earlier that without pulse-alsa... > > I've tried to increase the size of the buffers in PSoundChannelALSA::SetBuffers() and the playback > is much better, but that gives a bigger latency and delay when calling the echo test. > > > ------------------------------------------------------------------------ > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list From leamas.alec at gmail.com Sun Feb 22 10:07:56 2009 From: leamas.alec at gmail.com (Alec Leamas) Date: Sun, 22 Feb 2009 11:07:56 +0100 Subject: [Ekiga-list] Handling of old-fashioned phone numbers In-Reply-To: <1235294556.3960.1.camel@scorpion.multitel.be> References: <49A02B6F.9020308@gmail.com> <1235294556.3960.1.camel@scorpion.multitel.be> Message-ID: <49A123FC.1030108@gmail.com> Damien Sandras wrote: > [cut] > > If you do the back-end (as you have the most experience), we can do the > GUI (for Ekiga 3.4). Does that sound like a good idea for you? > Yes, I'll make a try, time permitting. And after a night's sleep, I've solved the UI issue :-). It's really just a question of accepting something like 0920-23456 in the ekiga URL window. When user clicks the "Call" button, the call is placed, and the complete URL is showed in the window. Errors handled as today. This means that the only new UI would be the ekiga-callto-config window, propably just yet another heading in Preferences. I'll add a screenshot of the configuration to the ekiga-callto homepage for reference. From f.vonbock at gmail.com Sun Feb 22 14:01:35 2009 From: f.vonbock at gmail.com (Fedor vonBock) Date: Sun, 22 Feb 2009 17:01:35 +0300 Subject: [Ekiga-list] ekiga timeout - eeebuntu In-Reply-To: <1235113571.4044.0.camel@scorpion.multitel.be> References: <1234977878.11150.22.camel@scorpion.multitel.be> <1235062542.23177.4.camel@scorpion.multitel.be> <1235113571.4044.0.camel@scorpion.multitel.be> Message-ID: hey damien, check it out 2009/02/22 16:57:17.330 0:09.279 Housekeeper SIP Transaction 4 SUBSCRIBE timeout, making retry 2 2009/02/22 16:57:17.330 0:09.279 Housekeeper SIP Sending PDU on udp$86.64.162.35:5060 SUBSCRIBE sip:alikhalfan1 at ekiga.net SIP/2.0 CSeq: 4 SUBSCRIBE Via: SIP/2.0/UDP 84.255.188.217:5066 ;branch=z9hG4bKa68a7461-56ff-dd11-82c6-0015afe7d424;rport User-Agent: Ekiga/2.0.12 From: >;tag=32817461-56ff-dd11-82c6-0015afe7d424 Call-ID: 861a4b61-56ff-dd11-82c6-0015afe7d424 at khalfan-laptop To: > Contact: Accept: application/simple-message-summary Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Expires: 3600 Event: message-summary Content-Length: 0 Max-Forwards: 70 2009/02/22 16:57:18.170 0:10.119 Housekeeper SIP Transaction 1 REGISTER timeout, making retry 3 2009/02/22 16:57:18.171 0:10.120 Housekeeper SIP Sending PDU on udp$62.4.81.180:5060 REGISTER sip:eugw.ast.diamondcard.us SIP/2.0 CSeq: 1 REGISTER Via: SIP/2.0/UDP 84.255.188.217:5063 ;branch=z9hG4bKfc87c260-56ff-dd11-82c6-0015afe7d424;rport User-Agent: Ekiga/2.0.12 From: >;tag=3e7dc260-56ff-dd11-82c6-0015afe7d424 Call-ID: 0c7a9360-56ff-dd11-82c6-0015afe7d424 at khalfan-laptop To: > Contact: Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Expires: 3600 Content-Length: 0 Max-Forwards: 70 2009/02/22 16:57:18.462 0:10.411 Housekeeper SIP Transaction 2 SUBSCRIBE timeout, making retry 3 2009/02/22 16:57:18.462 0:10.411 Housekeeper SIP Sending PDU on udp$62.4.81.180:5060 SUBSCRIBE sip:324278 at eugw.ast.diamondcard.usSIP/2.0 CSeq: 2 SUBSCRIBE Via: SIP/2.0/UDP 84.255.188.217:5064 ;branch=z9hG4bKfe16f060-56ff-dd11-82c6-0015afe7d424;rport User-Agent: Ekiga/2.0.12 From: >;tag=620df060-56ff-dd11-82c6-0015afe7d424 Call-ID: cc21c760-56ff-dd11-82c6-0015afe7d424 at khalfan-laptop To: > Contact: Accept: application/simple-message-summary Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Expires: 3600 Event: message-summary Content-Length: 0 Max-Forwards: 70 2009/02/22 16:57:19.014 0:10.963 Housekeeper SIP Transaction 3 REGISTER timeout, making retry 3 2009/02/22 16:57:19.014 0:10.963 Housekeeper SIP Sending PDU on udp$86.64.162.35:5060 REGISTER sip:ekiga.net SIP/2.0 CSeq: 3 REGISTER Via: SIP/2.0/UDP 84.255.188.217:5065 ;branch=z9hG4bKbea84361-56ff-dd11-82c6-0015afe7d424;rport User-Agent: Ekiga/2.0.12 From: >;tag=6ca04361-56ff-dd11-82c6-0015afe7d424 Call-ID: 045b1961-56ff-dd11-82c6-0015afe7d424 at khalfan-laptop To: > Contact: Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Expires: 3600 Content-Length: 0 Max-Forwards: 70 2009/02/22 16:57:19.330 0:11.279 Housekeeper SIP Transaction 4 SUBSCRIBE timeout, making retry 3 2009/02/22 16:57:19.330 0:11.279 Housekeeper SIP Sending PDU on udp$86.64.162.35:5060 SUBSCRIBE sip:alikhalfan1 at ekiga.net SIP/2.0 CSeq: 4 SUBSCRIBE Via: SIP/2.0/UDP 84.255.188.217:5066 ;branch=z9hG4bKa68a7461-56ff-dd11-82c6-0015afe7d424;rport User-Agent: Ekiga/2.0.12 From: >;tag=32817461-56ff-dd11-82c6-0015afe7d424 Call-ID: 861a4b61-56ff-dd11-82c6-0015afe7d424 at khalfan-laptop To: > Contact: Accept: application/simple-message-summary Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Expires: 3600 Event: message-summary Content-Length: 0 Max-Forwards: 70 2009/02/22 16:57:20.662 0:12.611 Housekeeper SIP Set state Terminated_Timeout for transaction 1 REGISTER 2009/02/22 16:57:20.966 0:12.915 Housekeeper SIP Set state Terminated_Timeout for transaction 2 SUBSCRIBE 2009/02/22 16:57:21.510 0:13.459 Housekeeper SIP Set state Terminated_Timeout for transaction 3 REGISTER 2009/02/22 16:57:21.834 0:13.783 Housekeeper SIP Set state Terminated_Timeout for transaction 4 SUBSCRIBE ^CKilled On Fri, Feb 20, 2009 at 10:06 AM, Damien Sandras wrote: > Le vendredi 20 f?vrier 2009 ? 09:47 +0300, Fedor vonBock a ?crit : > > now it says stun detects cone nat when i press detect nat type > > > > Please provide a full log 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 > > > _______________________________________________ > 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 mariofutire at googlemail.com Sun Feb 22 14:38:48 2009 From: mariofutire at googlemail.com (Andrea) Date: Sun, 22 Feb 2009 14:38:48 +0000 Subject: [Ekiga-list] A comparison ALSA-PULSE In-Reply-To: <49A11F5A.7090908@gmail.com> References: <49A11F5A.7090908@gmail.com> Message-ID: Alec Leamas wrote: > Just some thoughts. Maybe it can provoke someone who knows better... If > we had a pointer to cress-referenced code of the *dump routines we would > be on much safer ground. Sorry, I don't understand what you mean. > > It would be interesting to know the basic characteristics: sample rate, > frame size, samplesize, period size...I remember something like cat > /proc/asound/card0/pcm0p/sub0/hw_params, cat > /proc/asound/card0/pcm0c/sub0/sw_params to get this info. It is at the beginning of the 2 files (the same): Its setup is: stream : PLAYBACK access : RW_INTERLEAVED format : S16_LE subformat : STD channels : 2 rate : 44100 exact rate : 44100 (44100/1) msbits : 16 buffer_size : 1764 period_size : 441 period_time : 10000 tstamp_mode : NONE period_step : 1 avail_min : 441 period_event : 0 start_threshold : 1 stop_threshold : 1764 silence_threshold: 0 silence_size : 0 boundary : 1849688064 As a comparison this is what alsa's aplay uses when playing the same file Its setup is: stream : PLAYBACK access : RW_INTERLEAVED format : S16_LE subformat : STD channels : 2 rate : 44100 exact rate : 44100 (44100/1) msbits : 16 buffer_size : 22050 period_size : 5512 period_time : 125000 tstamp_mode : NONE period_step : 1 avail_min : 5512 period_event : 0 start_threshold : 22050 stop_threshold : 22050 silence_threshold: 0 silence_size : 0 boundary : 1445068800 > I interpret delay as the time the calling routine has to sit waiting > until there is space enough in the hardware buffer to write. > Available reflects the numbers of (bytes? frames? samples?) available > in the hw buffer for the sound card? > > Available_max: isn't this just the size of the hw buffer, in something( > bytes? frames? samples?) i. e., the max number of entities which could > be buffered? I am not sure I follow, since there are 2 patterns here alsa-pulse-alsa: delay = 0, avail_max=1764 and avail in between alsa direct: delay + avail = 1764, avail_max varies 1764 seems to be the size of the hw buffer. > > Isn't "trigger time" the time between each interrupt, basically the > thing you are waiting for in snd_pcm_wait()? > > Is pulseaudio running with high nice value? I use the default, no idea what to check here. > > Is the RTP jitter buffer a separate buffer, or is it using the alsa > buffer for this purpose? Separate playback buffers is a major drawback, > they add latency without being available to avoid underruns. Maybe it's > possible to increase the alsa buffer and decrease the RTP playback > buffer? Same latency, but less chance of underrun... There are > real-world examples of hw buffers ~3600 bytes, with very acceptable > latency (i. e., twice the buffer size here). But then that's the only > buffers.... and it depends on samplerate etc. Sorry, but this goes beyond my current understanding. > Alsa underruns behaves very differently depending on the calling > routines. I don't know whether pulse handles underruns internally (they > should!), or if it's a requirement for client code. Is this sorted out? > Not sure. > Skype runs fine with pulseaudio drivers, so it's definitely possible... Maybe you could dump the setup used by skype, via some /proc/file... From leamas.alec at gmail.com Sun Feb 22 16:00:24 2009 From: leamas.alec at gmail.com (Alec Leamas) Date: Sun, 22 Feb 2009 17:00:24 +0100 Subject: [Ekiga-list] A comparison ALSA-PULSE In-Reply-To: References: <49A11F5A.7090908@gmail.com> Message-ID: <49A17698.6020000@gmail.com> Andrea wrote: > Alec Leamas wrote: > >> Just some thoughts. Maybe it can provoke someone who knows better... If >> we had a pointer to cress-referenced code of the *dump routines we would >> be on much safer ground. >> > > Sorry, I don't understand what you mean. > Sorry, tapping the keyboard to fast. I mean a HTMl view of the soure code, where the different functions, definitions etc are clickable links (as created by e. g., Doxygen) > >> It would be interesting to know the basic characteristics: sample rate, >> frame size, samplesize, period size...I remember something like cat >> /proc/asound/card0/pcm0p/sub0/hw_params, cat >> /proc/asound/card0/pcm0c/sub0/sw_params to get this info. >> > > It is at the beginning of the 2 files (the same): > > Its setup is: > stream : PLAYBACK > access : RW_INTERLEAVED > format : S16_LE > subformat : STD > channels : 2 > rate : 44100 > exact rate : 44100 (44100/1) > msbits : 16 > buffer_size : 1764 > period_size : 441 > period_time : 10000 > tstamp_mode : NONE > period_step : 1 > avail_min : 441 > period_event : 0 > start_threshold : 1 > stop_threshold : 1764 > silence_threshold: > silence_size : 0 > boundary : 1849688064 > Trying to sort this out: I presume the buffer size is 1764 bytes, and there is two channels (i. e., stereo sound). This might mean that the buffer is just one period (441 frames/period * 2 samples/frame * 2 bytes/sample = 1764 bytes). This gives the buffer time 441/44100 => 10000 ns = 10 ms. That would be a really small buffer, Given an overall requirement of a latency in the 100-150ms area, it's not important. It should be possible to have 2 or three periods without any trouble. If there's latency, it's somewhere else... in the network, or possibly in other sw buffers (RTP?). If I'm right. This needs a review! I'm far from certain. > As a comparison this is what alsa's aplay uses when playing the same file > > Its setup is: > stream : PLAYBACK > access : RW_INTERLEAVED > format : S16_LE > subformat : STD > channels : 2 > rate : 44100 > exact rate : 44100 (44100/1) > msbits : 16 > buffer_size : 22050 > period_size : 5512 > period_time : 125000 > tstamp_mode : NONE > period_step : 1 > avail_min : 5512 > period_event : 0 > start_threshold : 22050 > stop_threshold : 22050 > silence_threshold: 0 > silence_size : 0 > boundary : 1445068800 > > aplay is an entirely different issue. They don't have to think about latency, just quality. So they make the buffers really large. A VOIP application must make a tradeoff between latency and quality. (And that's why it makes sense to adjust buffer size to network quality). >> I interpret delay as the time the calling routine has to sit waiting >> until there is space enough in the hardware buffer to write. >> Available reflects the numbers of (bytes? frames? samples?) available >> in the hw buffer for the sound card? >> >> Available_max: isn't this just the size of the hw buffer, in something( >> bytes? frames? samples?) i. e., the max number of entities which could >> be buffered? >> > > I am not sure I follow, since there are 2 patterns here > > alsa-pulse-alsa: delay = 0, avail_max=1764 and avail in between > alsa direct: delay + avail = 1764, avail_max varies > > 1764 seems to be the size of the hw buffer > Nor do I. I was just plain wrong in this, it seems. I have some experience with alsa, but have only used pulseaudio as user... stay tuned, I have som reading to do... > >> Isn't "trigger time" the time between each interrupt, basically the >> thing you are waiting for in snd_pcm_wait()? >> >> Is pulseaudio running with high nice value? >> I use the default, no idea what to check here >> > If you kill the daemon (pulseaudio --kill) and restart ir from a terminal (pulseaudio -D) you might get something like this if there's a problem:I: > caps.c: Limited capabilities successfully to CAP_SYS_NICE. > I: caps.c: Dropping root privileges. > I: caps.c: Limited capabilities successfully to CAP_SYS_NICE. > N: main.c: Called SUID root and real-time and/or high-priority scheduling was requested in the configuration. However, we lack the necessary privileges: > N: main.c: We are not in group 'pulse-rt', PolicyKit refuse to grant us the requested privileges and we have no increase RLIMIT_NICE/RLIMIT_RTPRIO resource limits. > N: main.c: For enabling real-time/high-priority scheduling please acquire the appropriate PolicyKit privileges, or become a member of 'pulse-rt', or increase the RLIMIT_NICE/RLIMIT_RTPRIO resource limits for this user. > >> Is the RTP jitter buffer a separate buffer, or is it using the alsa >> buffer for this purpose? Separate playback buffers is a major drawback, >> they add latency without being available to avoid underruns. Maybe it's >> possible to increase the alsa buffer and decrease the RTP playback >> buffer? Same latency, but less chance of underrun... There are >> real-world examples of hw buffers ~3600 bytes, with very acceptable >> latency (i. e., twice the buffer size here). But then that's the only >> buffers.... and it depends on samplerate etc. >> > > Sorry, but this goes beyond my current understanding. > Hm... same for me, for sure. But someone need to have an overall understanding of the buffering, otherwise it's really hard to get things right. Anyone, out there? > >> Alsa underruns behaves very differently depending on the calling >> routines. I don't know whether pulse handles underruns internally (they >> should!), or if it's a requirement for client code. Is this sorted out? >> >> > > Not sure. > OK, that's a "no". Problem is that it's the same for me... Questions, questions. Sorry for bringing all this mess up, maybe it's not exactly on the spot for this issue. But I do think life would be easier if we had some answers. I'll make a (reasonable) try with the pulseaudio docs. The problem is that here are to many loose ends, we need to limit this (my fault). > >> Skype runs fine with pulseaudio drivers, so it's definitely possible... >> > > Maybe you could dump the setup used by skype, via some /proc/file... > I'll make a try. Stay tuned... And keep up this important work, it's great someone takes a look at this! From leamas.alec at gmail.com Sun Feb 22 16:15:03 2009 From: leamas.alec at gmail.com (Alec Leamas) Date: Sun, 22 Feb 2009 17:15:03 +0100 Subject: [Ekiga-list] A comparison ALSA-PULSE In-Reply-To: References: <49A11F5A.7090908@gmail.com> Message-ID: <49A17A07.1000504@gmail.com> > It is at the beginning of the 2 files (the same): > > Its setup is: > stream : PLAYBACK > access : RW_INTERLEAVED > format : S16_LE > subformat : STD > channels : 2 > rate : 44100 > exact rate : 44100 (44100/1) > msbits : 16 > buffer_size : 1764 > period_size : 441 > period_time : 10000 > tstamp_mode : NONE > period_step : 1 > avail_min : 441 > period_event : 0 > start_threshold : 1 > stop_threshold : 1764 > silence_threshold: 0 > silence_size : 0 > boundary : 1849688064 > > Actually, I thnk I'm wrong. If the buffer is 1764 frames:. Time for 1 frame = 1/44100 sec = 1000/44100 ms. Time for buffer 1764 * 1000/44100= 40 ms. So, it really not that small, and increasing it is a problem. From leamas.alec at gmail.com Sun Feb 22 17:30:41 2009 From: leamas.alec at gmail.com (Alec Leamas) Date: Sun, 22 Feb 2009 18:30:41 +0100 Subject: [Ekiga-list] A comparison ALSA-PULSE In-Reply-To: References: <49A11F5A.7090908@gmail.com> Message-ID: <49A18BC1.10405@gmail.com> [cut] >> Skype runs fine with pulseaudio drivers, so it's definitely possible... >> > > Maybe you could dump the setup used by skype, via some /proc/file... > [mk at hemulen ~]$ cat /proc/asound/card0/pcm0c/sub0/sw_params tstamp_mode: NONE period_step: 1 avail_min: 512 start_threshold: 512 stop_threshold: 2147483647 silence_threshold: 0 silence_size: 1342177280 boundary: 1342177280 [mk at hemulen ~]$ cat /proc/asound/card0/pcm0p/sub0/hw_params access: RW_INTERLEAVED format: S16_LE subformat: STD channels: 2 rate: 48000 (48000/1) period_size: 512 buffer_size: 2560 [mk at hemulen ~]$ From mariofutire at googlemail.com Sun Feb 22 18:34:03 2009 From: mariofutire at googlemail.com (Andrea) Date: Sun, 22 Feb 2009 18:34:03 +0000 Subject: [Ekiga-list] A comparison ALSA-PULSE In-Reply-To: <49A17A07.1000504@gmail.com> References: <49A11F5A.7090908@gmail.com> <49A17A07.1000504@gmail.com> Message-ID: Alec Leamas wrote: > >> It is at the beginning of the 2 files (the same): >> >> Its setup is: >> stream : PLAYBACK >> access : RW_INTERLEAVED >> format : S16_LE >> subformat : STD >> channels : 2 >> rate : 44100 >> exact rate : 44100 (44100/1) >> msbits : 16 >> buffer_size : 1764 >> period_size : 441 >> period_time : 10000 >> tstamp_mode : NONE >> period_step : 1 >> avail_min : 441 >> period_event : 0 >> start_threshold : 1 >> stop_threshold : 1764 >> silence_threshold: 0 >> silence_size : 0 >> boundary : 1849688064 >> >> > Actually, I thnk I'm wrong. If the buffer is 1764 frames:. Time for 1 > frame = 1/44100 sec = 1000/44100 ms. Time for buffer 1764 * 1000/44100= > 40 ms. So, it really not that small, and increasing it is a problem. Looking at the code in PSoundChannelALSA::Write(), where len=1764 /* the number of frames to read is the buffer length divided by the size of one frame */ r = snd_pcm_writei (os_handle, (char *) &buf2 [pos], len / frameBytes); I would say 1764 is a number of bytes. The header file confirms this virtual PBoolean Write( const void * buf, ///< Pointer to a block of memory to write. PINDEX len ///< Number of bytes to write. ); From leamas.alec at gmail.com Sun Feb 22 19:33:38 2009 From: leamas.alec at gmail.com (Alec Leamas) Date: Sun, 22 Feb 2009 20:33:38 +0100 Subject: [Ekiga-list] A comparison ALSA-PULSE In-Reply-To: References: <49A11F5A.7090908@gmail.com> <49A17A07.1000504@gmail.com> Message-ID: <49A1A892.8020301@gmail.com> Andrea wrote: > Alec Leamas wrote: > >>> It is at the beginning of the 2 files (the same): >>> >>> Its setup is: >>> stream : PLAYBACK >>> access : RW_INTERLEAVED >>> format : S16_LE >>> subformat : STD >>> channels : 2 >>> rate : 44100 >>> exact rate : 44100 (44100/1) >>> msbits : 16 >>> buffer_size : 1764 >>> period_size : 441 >>> period_time : 10000 >>> tstamp_mode : NONE >>> period_step : 1 >>> avail_min : 441 >>> period_event : 0 >>> start_threshold : 1 >>> stop_threshold : 1764 >>> silence_threshold: 0 >>> silence_size : 0 >>> boundary : 1849688064 >>> >>> >>> >> Actually, I thnk I'm wrong. If the buffer is 1764 frames:. Time for 1 >> frame = 1/44100 sec = 1000/44100 ms. Time for buffer 1764 * 1000/44100= >> 40 ms. So, it really not that small, and increasing it is a problem. >> > > Looking at the code in PSoundChannelALSA::Write(), where len=1764 > > /* the number of frames to read is the buffer length > divided by the size of one frame */ > r = snd_pcm_writei (os_handle, (char *) &buf2 [pos], len / frameBytes); > > I would say 1764 is a number of bytes. > > The header file confirms this > > virtual PBoolean Write( > const void * buf, ///< Pointer to a block of memory to write. > PINDEX len ///< Number of bytes to write. > ); > There are really two things here: the total size of the hw buffer, and the size of a period. Data is transferred in chunks of one period, that's what's called buffer size in this code as I see it. The buffer is actually four periods, period time is 10000 ns = 10ms. So everything seems to adjust to this model. To summarize, a period is 1764 bytes == buffer above, the total buffer is 1764 frames i. e., 7056 bytes. If I'm right, that is... After some serious googling I found a document I've used before. Maybe it could be of interest: http://www.stderr.org/doc/libasound2-doc/html/pcm.html . Note the hostname, it looks bad, but I actually trust these docs. From leamas.alec at gmail.com Sun Feb 22 21:42:50 2009 From: leamas.alec at gmail.com (Alec Leamas) Date: Sun, 22 Feb 2009 22:42:50 +0100 Subject: [Ekiga-list] Trunk compile errors Message-ID: <49A1C6DA.2070208@gmail.com> I'm running into troubles (below) compiling trunk. Is it just that it's broken, or is it something in my environment? I've tried both 7675 and 7677, same status. So I guess it's something by me. Anyone else with gcc 4.3? --alec ---------------------------------------------------------------- ndpoints/sip-endpoint.cpp:1044: error: ?class SIPHandler? has no member named ?GetTargetAddress? endpoints/sip-endpoint.cpp:1065: error: no matching function for call to ?Opal::Sip::EndPoint::GetDefaultRegisteredPartyName()? /usr/include/opal/sip/sipep.h:704: note: candidates are: virtual SIPURL SIPEndPoint::GetDefaultRegisteredPartyName(const OpalTransport&) endpoints/sip-endpoint.cpp:1044: error: ?class SIPHandler? has no member named ?GetTargetAddress? endpoints/sip-endpoint.cpp:1065: error: no matching function for call to ?Opal::Sip::EndPoint::GetDef gui/main.cpp: In function ?int main(int, char**, char**)?: gui/main.cpp:4628: error: cannot call member function ?void PProcess::PreInitialise(int, char**, char**)? without object From vinifera at riseup.net Sun Feb 22 21:44:43 2009 From: vinifera at riseup.net (vin) Date: Sun, 22 Feb 2009 22:44:43 +0100 Subject: [Ekiga-list] 473 Filtered destination In-Reply-To: <4952A74E.000001.00352@kamasutra> References: <4952A74E.000001.00352@kamasutra> Message-ID: <1235339083.8711.3.camel@kuzguz> Hello, when will be the ZRTP function released? Is where any hope, to get this important function? "Daniel Smertnig has been working on ZRTP support. This was also part of the Google SoC propositions, but unfortunately, it got rejected. I think that some people do not understand the importance of professional VoIP support for the GNOME desktop." http://blog.ekiga.net/?p=29 from August 29th, 2006 Thx vin From hoogland at gmail.com Sun Feb 22 23:35:04 2009 From: hoogland at gmail.com (Jason Hoogland) Date: Mon, 23 Feb 2009 09:35:04 +1000 Subject: [Ekiga-list] DTMF choice Message-ID: I'm using Ekiga on linux and am trying to help two friends working Ekiga for windows on xp. We've got one of them working with full video calls. The other cannot reach 500 at ekiga.net, it doesn't seem to be dialling out. Comparing the network settings of the two xp installations, the one thats working has SIP DTMF Mode: INFO H.323 DTMF Mode: String While the one thats not working has SIP DTMF Mode: RFC2833 H.323 DTMF Mode: Tone Might well be another problem, just trying to eliminate this. Could this be a problem? Jason From ntluu at yahoo.com Mon Feb 23 01:46:09 2009 From: ntluu at yahoo.com (Nghiep Luu) Date: Sun, 22 Feb 2009 17:46:09 -0800 (PST) Subject: [Ekiga-list] Ekiga 3.02 for Windows: Logitech QuickCam Pro9000 and choosing Default-SIP ? In-Reply-To: <1235062726.23177.14.camel@scorpion.multitel.be> Message-ID: <222464.96261.qm@web50704.mail.re2.yahoo.com> Damien, Could kindly remove me from the distribution list please? Nghiep(Dan)Luu --- On Thu, 2/19/09, Damien Sandras wrote: From: Damien Sandras Subject: Re: [Ekiga-list] Ekiga 3.02 for Windows: Logitech QuickCam Pro9000 and choosing Default-SIP ? To: "Ekiga mailing list" Date: Thursday, February 19, 2009, 11:58 AM Le mercredi 18 f?vrier 2009 ? 12:45 -0600, Michael Cronenworth a ?crit : > -------- Original Message -------- > Subject: Re: [Ekiga-list] Ekiga 3.02 for Windows: Logitech QuickCam > Pro9000 and choosing Default-SIP ? > From: Damien Sandras > To: hb at h-bauer.de, Ekiga mailing list > Date: 02/18/2009 11:25 AM > > > Le mardi 17 f?vrier 2009 ? 07:03 +0100, Hans Bauer a ?crit : > > > > That means there is a bug in the WDM driver of your webcam. Try > > upgrading it. > > > > But I will ask if people contributing to the WIN32 build can also build > > our 'DirectVideo' capture plugin. It might work with it. > > > Is that a separate library? Configure argument? I have DirectShow > capture compiled in and the Preferences dialog only shows WDM capture. There is probably a reason why it does not load in that case. Probably a compilation flag. -- _ 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 Eugen.Dedu at pu-pm.univ-fcomte.fr Mon Feb 23 08:33:07 2009 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Mon, 23 Feb 2009 09:33:07 +0100 Subject: [Ekiga-list] Ekiga 3.02 for Windows: Logitech QuickCam Pro9000 and choosing Default-SIP ? In-Reply-To: <222464.96261.qm@web50704.mail.re2.yahoo.com> References: <222464.96261.qm@web50704.mail.re2.yahoo.com> Message-ID: <49A25F43.8010007@pu-pm.univ-fcomte.fr> Nghiep Luu wrote: > Damien, > Could kindly remove me from the distribution list please? > Nghiep(Dan)Luu Please use the Web address below, at the end of that page you can unsubscribe. > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list -- Eugen From dsandras at seconix.com Mon Feb 23 09:01:51 2009 From: dsandras at seconix.com (Damien Sandras) Date: Mon, 23 Feb 2009 10:01:51 +0100 Subject: [Ekiga-list] ekiga timeout - eeebuntu In-Reply-To: References: <1234977878.11150.22.camel@scorpion.multitel.be> <1235062542.23177.4.camel@scorpion.multitel.be> <1235113571.4044.0.camel@scorpion.multitel.be> Message-ID: <1235379711.4302.16.camel@scorpion.multitel.be> Le dimanche 22 f?vrier 2009 ? 17:01 +0300, Fedor vonBock a ?crit : > hey damien, > > check it out It is still the same problem : > > 2009/02/22 16:57:17.330 0:09.279 Housekeeper > SIP Transaction 4 SUBSCRIBE timeout, making retry 2 > 2009/02/22 16:57:17.330 0:09.279 Housekeeper > SIP Sending PDU on udp$86.64.162.35:5060 $84.255.188.217:5066> > SUBSCRIBE sip:alikhalfan1 at ekiga.net SIP/2.0 > CSeq: 4 SUBSCRIBE > Via: SIP/2.0/UDP > 84.255.188.217:5066;branch=z9hG4bKa68a7461-56ff-dd11-82c6-0015afe7d424;rport > User-Agent: Ekiga/2.0.12 > From: > ;tag=32817461-56ff-dd11-82c6-0015afe7d424 > Call-ID: 861a4b61-56ff-dd11-82c6-0015afe7d424 at khalfan-laptop > To: > Contact: > Accept: application/simple-message-summary > Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE > Expires: 3600 > Event: message-summary > Content-Length: 0 > Max-Forwards: 70 > > > 2009/02/22 16:57:18.170 0:10.119 Housekeeper > SIP Transaction 1 REGISTER timeout, making retry 3 > 2009/02/22 16:57:18.171 0:10.120 Housekeeper > SIP Sending PDU on udp$62.4.81.180:5060 > REGISTER sip:eugw.ast.diamondcard.us SIP/2.0 > CSeq: 1 REGISTER > Via: SIP/2.0/UDP > 84.255.188.217:5063;branch=z9hG4bKfc87c260-56ff-dd11-82c6-0015afe7d424;rport > User-Agent: Ekiga/2.0.12 > From: > ;tag=3e7dc260-56ff-dd11-82c6-0015afe7d424 > Call-ID: 0c7a9360-56ff-dd11-82c6-0015afe7d424 at khalfan-laptop > To: > Contact: > Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE > Expires: 3600 > Content-Length: 0 > Max-Forwards: 70 > > > 2009/02/22 16:57:18.462 0:10.411 Housekeeper > SIP Transaction 2 SUBSCRIBE timeout, making retry 3 > 2009/02/22 16:57:18.462 0:10.411 Housekeeper > SIP Sending PDU on udp$62.4.81.180:5060 > SUBSCRIBE sip:324278 at eugw.ast.diamondcard.us SIP/2.0 > CSeq: 2 SUBSCRIBE > Via: SIP/2.0/UDP > 84.255.188.217:5064;branch=z9hG4bKfe16f060-56ff-dd11-82c6-0015afe7d424;rport > User-Agent: Ekiga/2.0.12 > From: > ;tag=620df060-56ff-dd11-82c6-0015afe7d424 > Call-ID: cc21c760-56ff-dd11-82c6-0015afe7d424 at khalfan-laptop > To: > Contact: > Accept: application/simple-message-summary > Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE > Expires: 3600 > Event: message-summary > Content-Length: 0 > Max-Forwards: 70 > > > 2009/02/22 16:57:19.014 0:10.963 Housekeeper > SIP Transaction 3 REGISTER timeout, making retry 3 > 2009/02/22 16:57:19.014 0:10.963 Housekeeper > SIP Sending PDU on udp$86.64.162.35:5060 $84.255.188.217:5065> > REGISTER sip:ekiga.net SIP/2.0 > CSeq: 3 REGISTER > Via: SIP/2.0/UDP > 84.255.188.217:5065;branch=z9hG4bKbea84361-56ff-dd11-82c6-0015afe7d424;rport > User-Agent: Ekiga/2.0.12 > From: > ;tag=6ca04361-56ff-dd11-82c6-0015afe7d424 > Call-ID: 045b1961-56ff-dd11-82c6-0015afe7d424 at khalfan-laptop > To: > Contact: > Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE > Expires: 3600 > Content-Length: 0 > Max-Forwards: 70 > > > 2009/02/22 16:57:19.330 0:11.279 Housekeeper > SIP Transaction 4 SUBSCRIBE timeout, making retry 3 > 2009/02/22 16:57:19.330 0:11.279 Housekeeper > SIP Sending PDU on udp$86.64.162.35:5060 $84.255.188.217:5066> > SUBSCRIBE sip:alikhalfan1 at ekiga.net SIP/2.0 > CSeq: 4 SUBSCRIBE > Via: SIP/2.0/UDP > 84.255.188.217:5066;branch=z9hG4bKa68a7461-56ff-dd11-82c6-0015afe7d424;rport > User-Agent: Ekiga/2.0.12 > From: > ;tag=32817461-56ff-dd11-82c6-0015afe7d424 > Call-ID: 861a4b61-56ff-dd11-82c6-0015afe7d424 at khalfan-laptop > To: > Contact: > Accept: application/simple-message-summary > Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE > Expires: 3600 > Event: message-summary > Content-Length: 0 > Max-Forwards: 70 > > > 2009/02/22 16:57:20.662 0:12.611 Housekeeper > SIP Set state Terminated_Timeout for transaction 1 REGISTER > 2009/02/22 16:57:20.966 0:12.915 Housekeeper > SIP Set state Terminated_Timeout for transaction 2 SUBSCRIBE > 2009/02/22 16:57:21.510 0:13.459 Housekeeper > SIP Set state Terminated_Timeout for transaction 3 REGISTER > 2009/02/22 16:57:21.834 0:13.783 Housekeeper > SIP Set state Terminated_Timeout for transaction 4 SUBSCRIBE > ^CKilled > > > On Fri, Feb 20, 2009 at 10:06 AM, Damien Sandras > wrote: > Le vendredi 20 f?vrier 2009 ? 09:47 +0300, Fedor vonBock a > ?crit : > > now it says stun detects cone nat when i press detect nat > type > > > > > Please provide a full log 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 > > > _______________________________________________ > 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 leamas.alec at gmail.com Mon Feb 23 11:53:46 2009 From: leamas.alec at gmail.com (Alec Leamas) Date: Mon, 23 Feb 2009 12:53:46 +0100 Subject: [Ekiga-list] A comparison ALSA-PULSE In-Reply-To: References: <49A11F5A.7090908@gmail.com> Message-ID: <49A28E4A.2090007@gmail.com> > Its setup is: > stream : PLAYBACK > access : RW_INTERLEAVED > format : S16_LE > subformat : STD > channels : 2 > rate : 44100 > exact rate : 44100 (44100/1) > msbits : 16 > buffer_size : 22050 > period_size : 5512 > period_time : 125000 > tstamp_mode : NONE > period_step : 1 > avail_min : 5512 > period_event : 0 > start_threshold : 22050 > stop_threshold : 22050 > silence_threshold: 0 > silence_size : 0 > boundary : 1445068800 > > >> I interpret delay as the time the calling routine has to sit waiting >> until there is space enough in the hardware buffer to write. >> Available reflects the numbers of (bytes? frames? samples?) available >> in the hw buffer for the sound card? >> >> Available_max: isn't this just the size of the hw buffer, in something( >> bytes? frames? samples?) i. e., the max number of entities which could >> be buffered? >> > > I am not sure I follow, since there are 2 patterns here > > alsa-pulse-alsa: delay = 0, avail_max=1764 and avail in between > alsa direct: delay + avail = 1764, avail_max varies > > 1764 seems to be the size of the hw buffer. > > OK, this is haunting me. To get some peace of mind I need to sort this out, at least for myself. From the alsa docs: snd_pcm_status_get_avail_max: Get maximum number of frames available from a PCM status container after last snd_pcm_status call. snd_pcm_status_get_avail: Number of frames ready to be read/written snd_pcm_status_get_delay: Delay is distance between current application frame position and sound frame position. It's positive and less than buffer size in normal situation, negative on playback underrun and greater than buffer size on capture overrun. ----------------------------------- So: "avail" is the number of frames the app (opal) can write to alsa. I doubt the other figures are relevant, and they might certainly be hard to define in the emulated alsa interface provided by pulse. Something is strange in the "direct" logs. Looking at the "avail" figures, its something like (after an initial phase): 459, 21, 446, 9, 443, 6, 446, 9, 483, 46, 444, 6, ...the pattern is obvious. I interpret it as something is out of phase between the app (opal?) and the alsa layer. Ideal, these figures should be something around 446, 444, 489, 444, ... ( application writes as soon as there is space to write one period). Possibly nothing is written when avail is small, but it's still not as it should be. BTW, the "direct" logs shows that avail_max don't excceds 1000 frames - it's roughly 800-900. If this is typical, it should be possible to decrease the buffer to 3 periods (1323 frames) without any significant underrun rate. But this is not important now. As for the alsa logs, the xruns are the endpoint when the avail drops in four steps: 1322, 882, 441, 0/xrun. This is almost exactly 3 periods, 2 periods, 1 period, xrun. It looks like the xrun occurs when avail drops to 0 - which is more than strange. Something is broken also here, I presume this is the same problem as in the "direct" case. It might be an idea to put some timestamps around the debug printouts just to make sure the very presence of them don't disturb the timing. I don't think so, but I once, when working with something similar, remember storing figures in a buffer only written now and then. It was most likely overkill. But just to be sure... I really wish I had more time. But as I see it, these printouts implies something strange in the current alsa handling, and that this propably ought to be sorted out before trying pulse. As usual, that's if I'm right...Isn't there any other alsa people out there? From mariofutire at googlemail.com Mon Feb 23 14:20:02 2009 From: mariofutire at googlemail.com (Andrea) Date: Mon, 23 Feb 2009 14:20:02 +0000 Subject: [Ekiga-list] A comparison ALSA-PULSE In-Reply-To: <49A28E4A.2090007@gmail.com> References: <49A11F5A.7090908@gmail.com> <49A28E4A.2090007@gmail.com> Message-ID: Alec Leamas wrote: > >> Its setup is: >> stream : PLAYBACK >> access : RW_INTERLEAVED >> format : S16_LE >> subformat : STD >> channels : 2 >> rate : 44100 >> exact rate : 44100 (44100/1) >> msbits : 16 >> buffer_size : 22050 >> period_size : 5512 >> period_time : 125000 >> tstamp_mode : NONE >> period_step : 1 >> avail_min : 5512 >> period_event : 0 >> start_threshold : 22050 >> stop_threshold : 22050 >> silence_threshold: 0 >> silence_size : 0 >> boundary : 1445068800 >> >> I attach more output. What you have seen so far was the log when ekiga plays the ring tone (by far the most damaged sound). When running the echo test the setup is different stream : PLAYBACK access : RW_INTERLEAVED format : S16_LE subformat : STD channels : 1 rate : 8000 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< exact rate : 8000 (8000/1) <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< msbits : 16 buffer_size : 800 period_size : 160 period_time : 20000 tstamp_mode : NONE period_step : 1 avail_min : 160 period_event : 0 start_threshold : 1 stop_threshold : 800 silence_threshold: 0 silence_size : 0 boundary : 1677721600 And I cannot see any underrun at all. My echo test uses PCMA. It is possible that with a better codec (i.e. higher rate that 8000), we see them again. Don't really know how to test. I would say that the quality of the echo test with or without pulse is the same (but being only 8000 Hz, it is already not perfect and more difficult to judge). All my tests so far have been run in debug, so the speed of ekiga/opal/ptlib is already lower the release. The quality of the ring tone is though more or less the same. I will try to rerun everything in release. I have 2 points 1) Is the following true: ekiga-pulse gives bad audio quality because there are underruns. So, if for some connection there are no underruns (e.g. my echo test) then, the quality is not expected to be lower than alsa-direct, and we should not complain about pulse. 2) If underruns are (the) evil (or at least the biggest problem), then it would be good to print some indication of how close to the underrun we are. Does alsa provide that? Is it already part of my log? I still have not fully understood your comments about the values printed in the log. I need to get familiar with the terminology. And I have not yet checked for overruns when reading from the microphone. Andrea -------------- next part -------------- A non-text attachment was scrubbed... Name: echo.direct.txt.gz Type: application/x-gzip Size: 11454 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: echo.pulse.txt.gz Type: application/x-gzip Size: 2359 bytes Desc: not available URL: From Eugen.Dedu at pu-pm.univ-fcomte.fr Mon Feb 23 16:07:45 2009 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Mon, 23 Feb 2009 17:07:45 +0100 Subject: [Ekiga-list] Trunk compile errors In-Reply-To: <49A1C6DA.2070208@gmail.com> References: <49A1C6DA.2070208@gmail.com> Message-ID: <49A2C9D1.50509@pu-pm.univ-fcomte.fr> Alec Leamas wrote: > I'm running into troubles (below) compiling trunk. Is it just that it's > broken, or is it something in my environment? I've tried both 7675 and > 7677, same status. So I guess it's something by me. Anyone else with gcc > 4.3? > > --alec > > ---------------------------------------------------------------- > ndpoints/sip-endpoint.cpp:1044: error: ?class SIPHandler? has no member > named ?GetTargetAddress? > endpoints/sip-endpoint.cpp:1065: error: no matching function for call to > ?Opal::Sip::EndPoint::GetDefaultRegisteredPartyName()? > /usr/include/opal/sip/sipep.h:704: note: candidates are: virtual SIPURL > SIPEndPoint::GetDefaultRegisteredPartyName(const OpalTransport&) > > endpoints/sip-endpoint.cpp:1044: error: ?class SIPHandler? has no member > named ?GetTargetAddress? > endpoints/sip-endpoint.cpp:1065: error: no matching function for call to > ?Opal::Sip::EndPoint::GetDef > > gui/main.cpp: In function ?int main(int, char**, char**)?: > gui/main.cpp:4628: error: cannot call member function ?void > PProcess::PreInitialise(int, char**, char**)? without object Latest trunk for ptlib/opal/ekiga compile fine here. gcc 4.3.3. Tried 7681. Do you have trunk for ptlib/opal/ekiga? -- Eugen From leamas.alec at gmail.com Mon Feb 23 18:22:23 2009 From: leamas.alec at gmail.com (Alec Leamas) Date: Mon, 23 Feb 2009 19:22:23 +0100 Subject: [Ekiga-list] Trunk compile errors In-Reply-To: <49A2C9D1.50509@pu-pm.univ-fcomte.fr> References: <49A1C6DA.2070208@gmail.com> <49A2C9D1.50509@pu-pm.univ-fcomte.fr> Message-ID: <49A2E95F.6040209@gmail.com> Eugen Dedu wrote: > Alec Leamas wrote: >> I'm running into troubles (below) compiling trunk. Is it just that >> it's broken, or is it something in my environment? I've tried both >> 7675 and 7677, same status. So I guess it's something by me. Anyone >> else with gcc 4.3? >> >> --alec >> >> ---------------------------------------------------------------- >> ndpoints/sip-endpoint.cpp:1044: error: ?class SIPHandler? has no >> member named ?GetTargetAddress? >> endpoints/sip-endpoint.cpp:1065: error: no matching function for call >> to ?Opal::Sip::EndPoint::GetDefaultRegisteredPartyName()? >> /usr/include/opal/sip/sipep.h:704: note: candidates are: virtual >> SIPURL SIPEndPoint::GetDefaultRegisteredPartyName(const OpalTransport&) >> >> endpoints/sip-endpoint.cpp:1044: error: ?class SIPHandler? has no >> member named ?GetTargetAddress? >> endpoints/sip-endpoint.cpp:1065: error: no matching function for call >> to ?Opal::Sip::EndPoint::GetDef >> >> gui/main.cpp: In function ?int main(int, char**, char**)?: >> gui/main.cpp:4628: error: cannot call member function ?void >> PProcess::PreInitialise(int, char**, char**)? without object > > Latest trunk for ptlib/opal/ekiga compile fine here. gcc 4.3.3. > Tried 7681. > > Do you have trunk for ptlib/opal/ekiga? > Yes. But I've been able to build against the official Fedora RPM:s for opal and ptlib.... There is something lurking around here, but I'm happy for the moment. I'm busy anyway, as you may have noticed ;-) From jltarplin at hotmail.com Mon Feb 23 19:54:19 2009 From: jltarplin at hotmail.com (Joshua Tarplin) Date: Mon, 23 Feb 2009 14:54:19 -0500 Subject: [Ekiga-list] Newbie questions Message-ID: Question #1: Where can I find the FAQ for this maillist? Question #2: Assuming it's not one of the questions answered in the FAQ, what binary should I download for use on OpenSuSE 11.1? The Ekiga web page lists only those for BSD, OpenSolaris, Windows...and the sources, of course. Much thanks in advance... Joshua -------------- next part -------------- An HTML attachment was scrubbed... URL: From leamas.alec at gmail.com Mon Feb 23 20:21:47 2009 From: leamas.alec at gmail.com (Alec Leamas) Date: Mon, 23 Feb 2009 21:21:47 +0100 Subject: [Ekiga-list] A comparison ALSA-PULSE ( long) In-Reply-To: References: <49A11F5A.7090908@gmail.com> <49A28E4A.2090007@gmail.com> Message-ID: <49A3055B.8050904@gmail.com> Andrea wrote: > Alec Leamas wrote: > >>> Its setup is: >>> stream : PLAYBACK >>> access : RW_INTERLEAVED >>> format : S16_LE >>> subformat : STD >>> channels : 2 >>> rate : 44100 >>> exact rate : 44100 (44100/1) >>> msbits : 16 >>> buffer_size : 22050 >>> period_size : 5512 >>> period_time : 125000 >>> tstamp_mode : NONE >>> period_step : 1 >>> avail_min : 5512 >>> period_event : 0 >>> start_threshold : 22050 >>> stop_threshold : 22050 >>> silence_threshold: 0 >>> silence_size : 0 >>> boundary : 1445068800 >>> >>> >>> > > I attach more output. > What you have seen so far was the log when ekiga plays the ring tone (by far the most damaged sound). > When running the echo test the setup is different > > stream : PLAYBACK > access : RW_INTERLEAVED > format : S16_LE > subformat : STD > channels : 1 > rate : 8000 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< > exact rate : 8000 (8000/1) <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< > msbits : 16 > buffer_size : 800 > period_size : 160 > period_time : 20000 > tstamp_mode : NONE > period_step : 1 > avail_min : 160 > period_event : 0 > start_threshold : 1 > stop_threshold : 800 > silence_threshold: 0 > silence_size : 0 > boundary : 1677721600 > > And I cannot see any underrun at all. My echo test uses PCMA. It is possible that with a better > codec (i.e. higher rate that 8000), we see them again. Don't really know how to test. > > I would say that the quality of the echo test with or without pulse is the same (but being only 8000 > Hz, it is already not perfect and more difficult to judge). > > All my tests so far have been run in debug, so the speed of ekiga/opal/ptlib is already lower the > release. The quality of the ring tone is though more or less the same. I will try to rerun > everything in release. > > I have 2 points > > 1) Is the following true: ekiga-pulse gives bad audio quality because there are underruns. > So, if for some connection there are no underruns (e.g. my echo test) then, the quality is not > expected to be lower than alsa-direct, and we should not complain about pulse. > Yes. And, whatever the problems are, I don't really think it's pulse. I think it's a problem how we handle alsa which is just not that visible today. > 2) If underruns are (the) evil (or at least the biggest problem), then it would be good to print > some indication of how close to the underrun we are. Does alsa provide that? Is it already part of > my log? > Yes, in the max_avail, see below. But bear in mind that it's not only a question about if underruns happens, it's also a question how they are handled. Actually, a correct working upper layer (opal...) should never allow alsa underruns, it should rebuffer (send previous data) if nothing else is available. It's sounds much better than an actual underrun. > I still have not fully understood your comments about the values printed in the log. I need to get > familiar with the terminology. > > And I have not yet checked for overruns when reading from the microphone. > > Andrea > OK, as long you don't feel I occupy your territory, I'll make a try. After some reading my memories are coming back. But don't take what I say for granted, this *is* complicated. And if anyone who really knows alsa could review this, I would be more than happy... First of all: Alsa is basically, in all interfaces, concerned with frames. A frame is what the hardware handles in parallel. So in a mono stream, a frame is the same as a sample. In a stereo stream, a frame is two samples. The sample is S16_LE (signed 16 bit litte endian) i e, two bytes. So a frame is four bytes when sending the sound (stereo) and two bytes when talking as above (one channel, mono). The next entity is a period. A period is (in this context) a chunk of data transferred from user space to the alsa drivers' hw ringbuffer. The ringbuffer is normally an even number of periods. In the case above the period size is 160 frames. Since a frame is a sample ( mono), it's actually 320 bytes. But it's better to stick to frames, that's what alsa is all about. Last we have the hw bufffer. It's actually a ring buffer, where the application stores data, and the driver/interrupt routines fetches it and transfers it to the sound card. The overrun/underrun condtions is really what happens when the two ringbuffer pointers becomes equal, The period size is 160 frames. 1 frame takes 1/8000 seconds => 1000/8000 ms => period time 160/8 ms = 20 ms. The buffer above is actually 800/8 ms => 100 ms. This is quite a large buffer, with added network latency it might be to large. A goal is to keep the overall latency below 150 ms. The "avail" reflects the number of frames free to write in the hw buffer. When the buffer is full it's 0. When it's empty, it's the buffer size. The normal behaviour is that the application writes a period as soon as "avail" is >= 1 period. Sending routines should somehow (blocking I/O, event-driven) be sure that "avail" is indeed >= 1 period before it writes data. The avail_min is a threshold (for avail) where alsa activates the application. That is, an application which has done blocking I/O, or is wating for an event, is activated at this point. Here, it happens when it's possible to write a frame, which is perfectly reasonable. In your logs this should normally mean that "avail" is roughly 160-170 frames, there are some delays before the actual transfer takes place. The max_avail reflects indeed the maximum value of avail. It's really a quality measure. If it becomes as big as the buffer size (empty buffer) we are close to an underrun. If it's always much less than the buffer size, it should be possible to decrease the hw buffer. I think we can leave the other stuff aside, it's not important as I see it. Let me know if you think different. The strange thing in the alsa logs when sending the sound was that the "avail" was approaching 0 when the EPIPE signal triggered. Following the definitions above, this indicates an *overrun*. This is more than strange, it might very well be something I don't understand. Or something really weird somewhere. Perhaps the fact that this is a special case (stereo , sample rate) creates a mess? The "direct" log indicated that the application was about to write when avail is just 10-20 frames every second attempt. This should not happen, there should be at least a period free in the buffer before the application makes an attempt to write. Overall, the application seem to write at moments it shouldn't. How does the receiving party know the sample rate if the sounds are 16 kHz and the normal data 8 kHz? Looks odd to me, but I'm just a newbie in this... perhaps the RTP layer can handle this? Note the Skype settings: 48 kHz, buffer 2560 frames, stereo. 1 frame 1/48000 s == 1000/48000 ms => buffer time 2560/48 = 53 ms. Half the latency, and a better sound. Skype also uses the start_threshold. It means that the hardware starts automatically when start_threshold frames are ready to be sent to the sound card. It's a better way to start the thing than to start it explicitly as opal seems to do, it's a question of race conditions in the very beginning. Qutecom/Wengophone works with 16 kHz and a 60 ms buffer. Hey, we have some possibilities to improve Ekiga! Now, this was a long message :-) It's partly self-education, forgive me... --a From leamas.alec at gmail.com Mon Feb 23 21:17:05 2009 From: leamas.alec at gmail.com (Alec Leamas) Date: Mon, 23 Feb 2009 22:17:05 +0100 Subject: [Ekiga-list] A comparison ALSA-PULSE (long, addendum) In-Reply-To: References: <49A11F5A.7090908@gmail.com> <49A28E4A.2090007@gmail.com> Message-ID: <49A31251.3050103@gmail.com> When looking for quality info (underruns, other errors etc) it's really a question of what opal provides. It's there all errors are handled, and hopefully logged somehow. *If* opal is the lib handling alsa, which is just a guess from my side. From mtbc at ixod.org Mon Feb 23 21:21:24 2009 From: mtbc at ixod.org (Mark T.B. Carroll) Date: Mon, 23 Feb 2009 16:21:24 -0500 Subject: [Ekiga-list] A comparison ALSA-PULSE (long, addendum) In-Reply-To: <49A31251.3050103@gmail.com> (Alec Leamas's message of "Mon\, 23 Feb 2009 22\:17\:05 +0100") References: <49A11F5A.7090908@gmail.com> <49A28E4A.2090007@gmail.com> <49A31251.3050103@gmail.com> Message-ID: <874oyk7stn.fsf@ixod.org> Alec Leamas writes: > When looking for quality info (underruns, other errors etc) it's really > a question of what opal provides. It's there all errors are handled, and > hopefully logged somehow. *If* opal is the lib handling alsa, which is > just a guess from my side. Perhaps it's PTLib underneath it? I really don't know, I'm just throwing the idea out there! Mark From leamas.alec at gmail.com Mon Feb 23 21:38:44 2009 From: leamas.alec at gmail.com (Alec Leamas) Date: Mon, 23 Feb 2009 22:38:44 +0100 Subject: [Ekiga-list] A comparison ALSA-PULSE (long, addendum) In-Reply-To: <874oyk7stn.fsf@ixod.org> References: <49A11F5A.7090908@gmail.com> <49A28E4A.2090007@gmail.com> <49A31251.3050103@gmail.com> <874oyk7stn.fsf@ixod.org> Message-ID: <49A31764.1070808@gmail.com> Mark T.B. Carroll wrote: > Alec Leamas writes: > > >> When looking for quality info (underruns, other errors etc) it's really >> a question of what opal provides. It's there all errors are handled, and >> hopefully logged somehow. *If* opal is the lib handling alsa, which is >> just a guess from my side. >> > > Perhaps it's PTLib underneath it? I really don't know, I'm just throwing > the idea out there! > Indeed., grep tells it all. I have no more understanding than that the alsa functions are present there, and nowhere else. From Gene.Reed at Embarq.com Mon Feb 23 21:47:40 2009 From: Gene.Reed at Embarq.com (Reed, Gene R[EQ]) Date: Mon, 23 Feb 2009 15:47:40 -0600 Subject: [Ekiga-list] Newbie with questions... Message-ID: Hi all, First I've been lurking for some time, and going through the wiki, but still have some very basic questions. Please forgive me if the info is posted someplace and I have missed it, and point me to the location where it is documented. I am new to both linux and Ekiga. I have seen many references to editing the gconf file. Where is this file located? And am I correct that the gconf-editor is called from the command line? Based on the threads I've read, I believe the Ekiga config file is where I will find my solutions. Thanks, Gene -------------- next part -------------- An HTML attachment was scrubbed... URL: From mtbc at ixod.org Mon Feb 23 21:58:34 2009 From: mtbc at ixod.org (Mark T.B. Carroll) Date: Mon, 23 Feb 2009 16:58:34 -0500 Subject: [Ekiga-list] Newbie with questions... In-Reply-To: (Gene R. Reed's message of "Mon\, 23 Feb 2009 15\:47\:40 -0600") References: Message-ID: <87myccx1bp.fsf@ixod.org> "Reed, Gene R[EQ]" writes: > I am new to both linux and Ekiga. I have seen many references to > editing the gconf file. Where is this file located? For me it seems to be in ~/.gconf/apps/ekiga/ > And am I correct that the gconf-editor is called from the command > line? Yes; at least, that's how I do it. In the distribution I use (Debian) it was packaged separately so I had to install it separately. > Based on the threads I've read, I believe the Ekiga config file is > where I will find my solutions. That's good. (-: Mark From Eugen.Dedu at pu-pm.univ-fcomte.fr Mon Feb 23 22:01:43 2009 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Mon, 23 Feb 2009 23:01:43 +0100 Subject: [Ekiga-list] Newbie with questions... In-Reply-To: References: Message-ID: <49A31CC7.8040804@pu-pm.univ-fcomte.fr> Reed, Gene R[EQ] wrote: > Hi all, > > First I've been lurking for some time, and going through the wiki, but still have some very basic questions. Please forgive me if the info is posted someplace and I have missed it, and point me to the location where it is documented. > > I am new to both linux and Ekiga. I have seen many references to editing the gconf file. Where is this file located? And am I correct that the gconf-editor is called from the command line? > > Based on the threads I've read, I believe the Ekiga config file is where I will find my solutions. What do you want to do? -- Eugen From Eugen.Dedu at pu-pm.univ-fcomte.fr Mon Feb 23 22:05:38 2009 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Mon, 23 Feb 2009 23:05:38 +0100 Subject: [Ekiga-list] Newbie questions In-Reply-To: References: Message-ID: <49A31DB2.4010701@pu-pm.univ-fcomte.fr> Joshua Tarplin wrote: > Question #1: Where can I find the FAQ for this maillist? Maybe http://wiki.ekiga.org? > Question #2: Assuming it's not one of the questions answered in the > FAQ, what binary should I download for use on OpenSuSE 11.1? The > Ekiga web page lists only those for BSD, OpenSolaris, Windows...and > the sources, of course. We do not yet have a binary for OpenSUSE. Each distribution builds programs itself; it's not us who build for all distributions (with a few exceptions). Please check in their own repositories. Ask if you do not know how to do it. -- Eugen From Gene.Reed at Embarq.com Mon Feb 23 22:21:25 2009 From: Gene.Reed at Embarq.com (Reed, Gene R[EQ]) Date: Mon, 23 Feb 2009 16:21:25 -0600 Subject: [Ekiga-list] Newbie with questions... In-Reply-To: <49A31CC7.8040804@pu-pm.univ-fcomte.fr> References: <49A31CC7.8040804@pu-pm.univ-fcomte.fr> Message-ID: "What do you want to do?" I want to remove the STUN server from the file. Similar to what Bas did in the thread "[Ekiga-list] Problems incoming calls". At this point I cannot even get Ekiga to register with my provider; I expect it is STUN configuration causing the problem. I use Twinkle successfully with the option "NAT traversal not needed". I am running OpenSuSE 11.0. Thanks! -----Original Message----- Reed, Gene R[EQ] wrote: > Hi all, > > First I've been lurking for some time, and going through the wiki, but still have some very basic questions. Please forgive me if the info is posted someplace and I have missed it, and point me to the location where it is documented. > > I am new to both linux and Ekiga. I have seen many references to editing the gconf file. Where is this file located? And am I correct that the gconf-editor is called from the command line? > > Based on the threads I've read, I believe the Ekiga config file is where I will find my solutions. What do you want to do? -- Eugen _______________________________________________ ekiga-list mailing list ekiga-list at gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list From derek at indranet.co.nz Mon Feb 23 22:44:03 2009 From: derek at indranet.co.nz (Derek Smithies) Date: Tue, 24 Feb 2009 11:44:03 +1300 (NZDT) Subject: [Ekiga-list] A comparison ALSA-PULSE (long, addendum) In-Reply-To: <49A31764.1070808@gmail.com> References: <49A11F5A.7090908@gmail.com> <49A28E4A.2090007@gmail.com> <49A31251.3050103@gmail.com> <874oyk7stn.fsf@ixod.org> <49A31764.1070808@gmail.com> Message-ID: Hi, >> Perhaps it's PTLib underneath it? I really don't know, I'm just throwing >> the idea out there! It is PTLib which contains the code to read from alsa. Surely, the ideal is not to go via ALSA, but have ptlib directly talk to pulse. Thus, we need to write a ptlib plugin for pulse audio. We know how ptlib plugins work. There are example plugins for alsa, esd, oss, sunaudio. The big question is writing a plugin for pulse. What is involved in writing code that talks directly to pulse ? Anyone know example code, or of the pulse api docs? Please don't refer me to docs which say "just use alsa code". We are using alsa code, and that is why we are having this issue. Derek. Derek Smithies Ph.D. IndraNet Technologies Ltd. Email: derek at indranet.co.nz ph +64 3 365 6485 Web: http://www.indranet-technologies.com/ From jltarplin at hotmail.com Mon Feb 23 23:38:32 2009 From: jltarplin at hotmail.com (Joshua Tarplin) Date: Mon, 23 Feb 2009 18:38:32 -0500 Subject: [Ekiga-list] Newbie questions In-Reply-To: <49A31DB2.4010701@pu-pm.univ-fcomte.fr> References: <49A31DB2.4010701@pu-pm.univ-fcomte.fr> Message-ID: > > Question #2: Assuming it's not one of the questions answered in the > > FAQ, what binary should I download for use on OpenSuSE 11.1? The > > Ekiga web page lists only those for BSD, OpenSolaris, Windows...and > > the sources, of course. > > We do not yet have a binary for OpenSUSE. Each distribution builds > programs itself; it's not us who build for all distributions (with a few > exceptions). Please check in their own repositories. Ask if you do not > know how to do it. Merci, mon ami! Joshua -------------- next part -------------- An HTML attachment was scrubbed... URL: From leamas.alec at gmail.com Tue Feb 24 08:36:47 2009 From: leamas.alec at gmail.com (Alec Leamas) Date: Tue, 24 Feb 2009 09:36:47 +0100 Subject: [Ekiga-list] A comparison ALSA-PULSE (long, addendum) In-Reply-To: References: <49A11F5A.7090908@gmail.com> <49A28E4A.2090007@gmail.com> <49A31251.3050103@gmail.com> <874oyk7stn.fsf@ixod.org> <49A31764.1070808@gmail.com> Message-ID: <49A3B19F.1090605@gmail.com> Derek Smithies wrote: > Hi, >>> Perhaps it's PTLib underneath it? I really don't know, I'm just >>> throwing >>> the idea out there! > > It is PTLib which contains the code to read from alsa. > > Surely, the ideal is not to go via ALSA, but have ptlib directly talk > to pulse. Thus, we need to write a ptlib plugin for pulse audio. > > We know how ptlib plugins work. There are example plugins for alsa, > esd, oss, sunaudio. The big question is writing a plugin for pulse. > > What is involved in writing code that talks directly to pulse ? > Anyone know example code, or of the pulse api docs? > > Please don't refer me to docs which say "just use alsa code". We are > using alsa code, and that is why we are having this issue. > > Derek. I think you are right. For the reasons you mention, but also because the current alsa plugin is seriously flawed I made a short review very late yesterday. Among other things it's synchronized in a way that forces playback and record to wait for each others' I/O operations(!) With this said, I don't (yet) see any problems in understanding and using the external interface. These problems are within the alsa plugin. So: with limited resources we have a choice to either "fix" (i. e., major rewrite of) current alsa plugin, or make a pulse plugin. The latter is most likely easier. But then we leave platforms without pulse in the dark ages. So question is: do we need a working alsa plugin if we have a pulse one? Anyone? (let's take silence as a "no" :-) ) What disturbs me a little is the way the plugin interface "seems" to be, at least from the alsa example. Question is if there is a way to arrange event-driven I/O - current code is strictly polled. OTOH, we can live with that, for sure. But there "might* be other hooks in the plugin interface not used today... we might need to backwards-engineer some docs... possibly expanding the plugin interface in a backwards-compatible way.... There is good pulse doc's on their website e. g., http://0pointer.de/lennart/projects/pulseaudio/doxygen/ From dsandras at seconix.com Tue Feb 24 08:49:09 2009 From: dsandras at seconix.com (Damien Sandras) Date: Tue, 24 Feb 2009 09:49:09 +0100 Subject: [Ekiga-list] Newbie with questions... In-Reply-To: References: <49A31CC7.8040804@pu-pm.univ-fcomte.fr> Message-ID: <1235465349.3951.8.camel@scorpion.multitel.be> Le lundi 23 f?vrier 2009 ? 16:21 -0600, Reed, Gene R[EQ] a ?crit : > "What do you want to do?" > > I want to remove the STUN server from the file. Similar to what Bas did in the thread "[Ekiga-list] Problems incoming calls". At this point I cannot even get Ekiga to register with my provider; I expect it is STUN configuration causing the problem. We have added an option in the upcoming 3.2. > I use Twinkle successfully with the option "NAT traversal not needed". > Just use this command : gconftool-2 -s /apps/ekiga/general/nat/stun_server '' --type=string Never edit gconf files directly, it won't 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 leamas.alec at gmail.com Tue Feb 24 09:12:43 2009 From: leamas.alec at gmail.com (Alec Leamas) Date: Tue, 24 Feb 2009 10:12:43 +0100 Subject: [Ekiga-list] PTLIB alsa plugin status Message-ID: <49A3BA0B.3010805@gmail.com> I made a short review of the read/write code in the PTLIB alsa plugin yesterday. In short: - Playback and record thread are synchronized in a way that forces the two streams to wait for each others I/O operations. - There is no rebuffering support. This means data underruns sounds worse than necessary. - Various minor remarks. I've filed a bug against ekiga with some more details : http://bugzilla.gnome.org/show_bug.cgi?id=572953 (pls don't file a bug on the formatting of the attachment...). In my opinion, it's not really worth to put much work on using the current alsa plugin. As long as it works, don't touch it... until it get's fixed in a proper way, possibly by using a pulse plugin instead. As for the latency discussion about alsa vs pulse: This review shows that anything will be much better than current alsa code... --a From derek at indranet.co.nz Tue Feb 24 09:13:52 2009 From: derek at indranet.co.nz (Derek Smithies) Date: Tue, 24 Feb 2009 22:13:52 +1300 (NZDT) Subject: [Ekiga-list] A comparison ALSA-PULSE (long, addendum) In-Reply-To: <49A3B19F.1090605@gmail.com> References: <49A11F5A.7090908@gmail.com> <49A28E4A.2090007@gmail.com> <49A31251.3050103@gmail.com> <874oyk7stn.fsf@ixod.org> <49A31764.1070808@gmail.com> <49A3B19F.1090605@gmail.com> Message-ID: On Tue, 24 Feb 2009, Alec Leamas wrote: > Derek Smithies wrote: >> Hi, >>>> Perhaps it's PTLib underneath it? I really don't know, I'm just throwing >>>> the idea out there! >> >> It is PTLib which contains the code to read from alsa. >> >> Surely, the ideal is not to go via ALSA, but have ptlib directly talk to >> pulse. Thus, we need to write a ptlib plugin for pulse audio. >> >> We know how ptlib plugins work. There are example plugins for alsa, esd, >> oss, sunaudio. The big question is writing a plugin for pulse. >> >> What is involved in writing code that talks directly to pulse ? >> Anyone know example code, or of the pulse api docs? >> >> Please don't refer me to docs which say "just use alsa code". We are using >> alsa code, and that is why we are having this issue. >> >> Derek. > I think you are right. For the reasons you mention, but also because the > current alsa plugin is seriously flawed I made a short review very late > yesterday. Among other things it's synchronized in a way that forces playback > and record to wait for each others' I/O operations(!) Yes - I am aware of this mutex. Have you tried it with this synchronizing mutex removed? That mutex has been there since the the plugin was written. > > With this said, I don't (yet) see any problems in understanding and using the > external interface. These problems are within the alsa plugin. > So: with limited resources we have a choice to either "fix" (i. e., major > rewrite of) current alsa plugin, or make a pulse plugin. What is there to rewrite? There are only a few things that are possibly wrong - the synchronising mutex and what else? It is, as you say, copied from the alsa example docs.... > The latter is most likely easier. Not really... > But then we leave platforms without pulse in the dark ages. So > question is: do we need a working alsa plugin if we have a pulse one? Anyone? > (let's take silence as a "no" :-) ) A working alsa plugin is a requirement. There may only be 5 % of users using alsa, but they will scream loud and long if it does not work for them. Some x11 window environments don't have pulse audio in them. So you need pulse and alsa plugins. > > What disturbs me a little is the way the plugin interface "seems" to be, at > least from the alsa example. Question is if there is a way to arrange > event-driven I/O - current code is strictly polled. The current code is arranged so that *the application writes/reads a block of data to/from the sound device. *this process is timed by the sound device so that the write/read takes as long as the framesize of the codec. Thus, for GSM (20ms frame) the write/read takes 20ms. It is the sound device that times the sending of UDP packets to the remote endpoint. Software timers are very unreliable (in comparison to hardware timers, where the board/driver determines the read time as being "exactly" 20ms) Suppose we have 3 GSM frames in each UDP packet. This means that every 60ms (silence detection disabled) a UDP packet is sent to the remote node. To do the timing, there is a read of 320 bytes, which takes 20ms, encode of audio frame read of 320 bytes, which takes 20ms, encode of audio frame read of 320 bytes, which takes 20ms, encode of audio frame and the three encoded audio frames are placed in a UDP packet which is sent to the remote host. > OTOH, we can live with that, for sure. But there "might* be other hooks > in the plugin interface not used today... we might need to > backwards-engineer some docs... possibly expanding the plugin interface > in a backwards-compatible way.... Sounds pretty hard way to do things.. I think the PTlib developers won't be happy with expansion of the plugin interface.. > > There is good pulse doc's on their website e. g., > http://0pointer.de/lennart/projects/pulseaudio/doxygen/ Thanks for this. It is a more useful set of documentation than when I last looked for pulse-doc like things. -- Derek Smithies Ph.D. IndraNet Technologies Ltd. Email: derek at indranet.co.nz ph +64 3 365 6485 Web: http://www.indranet-technologies.com/ From derek at indranet.co.nz Tue Feb 24 09:22:04 2009 From: derek at indranet.co.nz (Derek Smithies) Date: Tue, 24 Feb 2009 22:22:04 +1300 (NZDT) Subject: [Ekiga-list] PTLIB alsa plugin status In-Reply-To: <49A3BA0B.3010805@gmail.com> References: <49A3BA0B.3010805@gmail.com> Message-ID: Hi, On Tue, 24 Feb 2009, Alec Leamas wrote: > > - Playback and record thread are synchronized in a way that forces the two > streams to wait for each others I/O operations. Yes - can someone test that ptlib alsa plugin works ok with this mutex removed?? > - There is no rebuffering support. This means data underruns sounds worse > than necessary. What is required to do rebuffering? Any code suggestions? > > In my opinion, it's not really worth to put much work on using the current > alsa plugin. As long as it works, don't touch it... until it get's fixed in a > proper way, possibly by using a pulse plugin instead. It is worth it. Alsa will be around for a long time. This is an opportunity for Ekiga people to contribute back to ptlib&opal (libraries that are crucial to this project) > As for the latency discussion about alsa vs pulse: This review shows that > anything will be much better than current alsa code... The current alsa code works mostly.. it is close.. If there was some usable docs at alsa to explain what is not good, that would help. Anyone able to work out what is actually wrong in the alsa plugin? Derek. -- Derek Smithies Ph.D. IndraNet Technologies Ltd. Email: derek at indranet.co.nz ph +64 3 365 6485 Web: http://www.indranet-technologies.com/ From leamas.alec at gmail.com Tue Feb 24 10:11:43 2009 From: leamas.alec at gmail.com (Alec Leamas) Date: Tue, 24 Feb 2009 11:11:43 +0100 Subject: [Ekiga-list] PTLIB alsa plugin status In-Reply-To: References: <49A3BA0B.3010805@gmail.com> Message-ID: <49A3C7DF.1060400@gmail.com> Derek Smithies wrote: > Hi, Hi :-) Have you checked the bugzilla bug? There's some more meat on the bones (or however you prefer to say it down there ;-) > On Tue, 24 Feb 2009, Alec Leamas wrote: >> >> - Playback and record thread are synchronized in a way that forces >> the two streams to wait for each others I/O operations. > Yes - can someone test that ptlib alsa plugin works ok with this mutex > removed?? It's not just a question of testing. This kind of problem must be handled by careful reading of code, to test all conditions possible when there are concurrent threads is not that simple. I think what should be done is to separate the recording and playback threads into separate objects, thus letting the compiler check that there are no critical zones. I also think the whole idea of a single "channel" must be interpreted as a facade for two more or less independent streams . They should not really share any data. But of course they share a lot of behaviour. > >> - There is no rebuffering support. This means data underruns sounds >> worse than necessary. > What is required to do rebuffering? Any code suggestions? Well, the basic thing is a separate thread feeding alsa started when alsa is started. The write routine just drops it's buffer to the thread through some kind of thread-safe mechanism, being blocked if there is no space in (a small) buffer. The thread is just waiting for alsa (snd:_pcm_wait). When started it normally transfers data from upstream (write), rebuffering as necessary if there is nothing else to send. > >> >> In my opinion, it's not really worth to put much work on using the >> current alsa plugin. As long as it works, don't touch it... until it >> get's fixed in a proper way, possibly by using a pulse plugin instead. > It is worth it. Alsa will be around for a long time. This is an > opportunity for Ekiga people to contribute back to ptlib&opal > (libraries that are crucial to this project) OK, unless you provoke you don't get an answer... I actually share your opinion :-) > >> As for the latency discussion about alsa vs pulse: This review shows >> that anything will be much better than current alsa code... > The current alsa code works mostly.. it is close.. If there was some > usable docs at alsa to explain what is not good, that would help. > Anyone able to work out what is actually wrong in the alsa plugin? But we have 100 ms of hw buffer, roughly twice the size of other VOIP applications. There are open issues about the overall design, threads, objects etc. There are no quality metrics, we have no idea about things like bytes transferred, hard errors, soft errors, buffer usage etc. And Andreas' logs shows that the driver does not deliver data as expected. I don't want to blame anyone or so, but I think we must face the fact that there *are* problems, some of them requiring more than a point fix. As I said, take a look at the bug, there are some more details, despite the horrible formatting. And bear in mind that I'm certainly wrong from time to time. And that English isn't my native language, the nuances are a bit bit, well, rough now and then :-) > > Derek. --alec From craigs at postincrement.com Tue Feb 24 10:34:05 2009 From: craigs at postincrement.com (Craig Southeren) Date: Tue, 24 Feb 2009 21:34:05 +1100 Subject: [Ekiga-list] A comparison ALSA-PULSE (long, addendum) In-Reply-To: References: <49A11F5A.7090908@gmail.com> <49A28E4A.2090007@gmail.com> <49A31251.3050103@gmail.com> <874oyk7stn.fsf@ixod.org> <49A31764.1070808@gmail.com> Message-ID: <49A3CD1D.5040703@postincrement.com> To all I have just noticed this thread. I wish someone had posted it on the Opal list, where Robert and I might have noticed it earlier :) We are currently planning to add a new audio and video device plugin interface to Opal. This new multimedia device interface will be similar to the current codec API (allowing plugins to be written without PTLib) and will support additional functionality such as: - support for devices that offer encoded media (such as pre-encoded video) - support for devices that offer both audio and video. One of the first plugins I intend to write is a new Pulse audio plugin, because Fedora uses pulseaudio by default, and I am sick of audio not working without lots of changes :) I'd welcome comments from anyone on these plans Craig Derek Smithies wrote: > Hi, >>> Perhaps it's PTLib underneath it? I really don't know, I'm just throwing >>> the idea out there! > > It is PTLib which contains the code to read from alsa. > > Surely, the ideal is not to go via ALSA, but have ptlib directly talk to > pulse. Thus, we need to write a ptlib plugin for pulse audio. > > We know how ptlib plugins work. There are example plugins for alsa, esd, > oss, sunaudio. The big question is writing a plugin for pulse. > > What is involved in writing code that talks directly to pulse ? > Anyone know example code, or of the pulse api docs? > > Please don't refer me to docs which say "just use alsa code". We are > using alsa code, and that is why we are having this issue. > > Derek. -- ----------------------------------------------------------------------- Craig Southeren Post Increment ? VoIP Consulting and Software craigs at postincrement.com.au www.postincrement.com.au Phone: +61 243654666 ICQ: #86852844 Fax: +61 243656905 MSN: craig_southeren at hotmail.com Mobile: +61 417231046 Jabber: craigs at jabber.org "Science is the poetry of reality." Richard Dawkins From Gene.Reed at Embarq.com Tue Feb 24 16:18:03 2009 From: Gene.Reed at Embarq.com (Reed, Gene R[EQ]) Date: Tue, 24 Feb 2009 10:18:03 -0600 Subject: [Ekiga-list] Newbie with questions... In-Reply-To: <1235465349.3951.8.camel@scorpion.multitel.be> References: <49A31CC7.8040804@pu-pm.univ-fcomte.fr> <1235465349.3951.8.camel@scorpion.multitel.be> Message-ID: I ran the command as you suggested, and I have upgraded to Ekiga v3.0.2. Results when I enable my account via account settings, "Could not register(Forbidden)". Any suggestions you may have would be appreciated. Gene -----Original Message----- From: ekiga-list-bounces at gnome.org [mailto:ekiga-list-bounces at gnome.org] On Behalf Of Damien Sandras Sent: Tuesday, February 24, 2009 2:49 AM To: Ekiga mailing list Subject: Re: [Ekiga-list] Newbie with questions... Le lundi 23 f?vrier 2009 ? 16:21 -0600, Reed, Gene R[EQ] a ?crit : > "What do you want to do?" > > I want to remove the STUN server from the file. Similar to what Bas did in the thread "[Ekiga-list] Problems incoming calls". At this point I cannot even get Ekiga to register with my provider; I expect it is STUN configuration causing the problem. We have added an option in the upcoming 3.2. > I use Twinkle successfully with the option "NAT traversal not needed". > Just use this command : gconftool-2 -s /apps/ekiga/general/nat/stun_server '' --type=string Never edit gconf files directly, it won't 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 _______________________________________________ ekiga-list mailing list ekiga-list at gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list From JDiamond at acadiau.ca Tue Feb 24 20:13:50 2009 From: JDiamond at acadiau.ca (Jim Diamond) Date: Tue, 24 Feb 2009 16:13:50 -0400 Subject: [Ekiga-list] ekiga on Slackware 12.2 not working usefully... any suggestions? Message-ID: <20090224201350.GA4297@jdiamond-nb> Hi I have recently tried ekiga 3.0.1 + opal 3.4.3 + ptlib 2.4.3 ekiga 3.0.2 + opal 3.4.4 + ptlib 2.4.4 ekiga 3.1.0 + opal 3.6.0 + ptlib 2.6.0 under Slackware 12.2 (various computers, various kernels). 3.1.0 doesn't let me use my Logitech QuickCam Pro for Notebooks (uvcvideo, needs V4L2 to work at all on my systems), so I gave up on that. The other two versions seem to behave similarly with respect to these problems: (1) The call recipient sees only his own video, the video of the caller is never visible. (2) If the caller is viewing his own video before making a call, when the call is established, he (apparently) alternately sees his own video frames and frames of the call recipient. In other words, the video picture is pretty much useless. If the two video resolutions are not the same, the (whole) window changes size with (apparently) each frame change, which adds to the annoyance. If the caller was not looking at his own video, he sees the call recipient's video fine. This behaviour happens regardless of which way the call goes. Neither the caller nor the recipient is able to change anything with the "View" menu items "Local Video", "Remote Video", "P-in-P" or "P-in-P in Separate Window". This is seen when both computers are on the same LAN, so I don't think there should be any issues with gateways/firewalls/... I am calling with addresses like "h323:192.168.1.4" This behaviour is also seen with other web cams, so I don't think the particular web cam(s) are relevant. This is pretty much a show stopper, so the fact that many people are happily using ekiga suggest to me that it must be "me", but I have no idea what I'm doing wrong. Older versions of ekiga worked fine for me on older versions of Slackware. Note that Slackware does not have gnome, so (following the SlackBuild at www.slackbuilds.org) I disable gnome and gconf support (which, as an aside, I consider to be a large improvement, since gconf has given me nothing but grief in the past). FYI, config.log records the following: ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --mandir=/u sr/man --disable-gnome --disable-gconf --disable-avahi --disable-gdu --disable-e ds --disable-static --build=i486-slackware-linux Any suggestions? I'm pretty much dead in the water here. I would be happy to try out any patches anyone can provide (3.0.2 and friends would probably be the best choice, given 3.1.0's recalcitrance). Thanks. Jim From derek at indranet.co.nz Tue Feb 24 20:38:33 2009 From: derek at indranet.co.nz (Derek Smithies) Date: Wed, 25 Feb 2009 09:38:33 +1300 (NZDT) Subject: [Ekiga-list] PTLIB alsa plugin status In-Reply-To: <49A3C7DF.1060400@gmail.com> References: <49A3BA0B.3010805@gmail.com> <49A3C7DF.1060400@gmail.com> Message-ID: Hi, >>> - Playback and record thread are synchronized in a way that forces the two >>> streams to wait for each others I/O operations. >> Yes - can someone test that ptlib alsa plugin works ok with this mutex >> removed?? This mutex is important, and should not syncrhonize the play&record threads. There are two PSoundChannel class instances active during a call. One for play. One for record. These PSoundChannel class instances are seperate, and have seperately opened connections to the sound_alsa plugin. Consequently, the mutex you refer to is not syncrhonising access to play&record. The mutex is locking access to play variables (device pointers) + play A different mutex instance is locking access to write variables (device pointers) + write. ================== Now, if the same PSoundChannel instance is used for play and record - (which can be achieved by bad application writing) then you have an application coding problem. I assume Ekiga does not have this issue. ========================================= > to blame anyone or so, but I think we must face the fact that there *are* > problems, some of them requiring more than a point fix. Agreed. Derek. On Tue, 24 Feb 2009, Alec Leamas wrote: > Derek Smithies wrote: >> Hi, > > Hi :-) > > Have you checked the bugzilla bug? There's some more meat on the bones (or > however you prefer to say it down there ;-) >> On Tue, 24 Feb 2009, Alec Leamas wrote: >>> >>> - Playback and record thread are synchronized in a way that forces the two >>> streams to wait for each others I/O operations. >> Yes - can someone test that ptlib alsa plugin works ok with this mutex >> removed?? > It's not just a question of testing. This kind of problem must be handled by > careful reading of code, to test all conditions possible when there are > concurrent threads is not that simple. I think what should be done is to > separate the recording and playback threads into separate objects, thus > letting the compiler check that there are no critical zones. I also think > the whole idea of a single "channel" must be interpreted as a facade for two > more or less independent streams . They should not really share any data. But > of course they share a lot of behaviour. >> >>> - There is no rebuffering support. This means data underruns sounds worse >>> than necessary. >> What is required to do rebuffering? Any code suggestions? > Well, the basic thing is a separate thread feeding alsa started when alsa is > started. The write routine just drops it's buffer to the thread through some > kind of thread-safe mechanism, being blocked if there is no space in (a > small) buffer. The thread is just waiting for alsa (snd:_pcm_wait). When > started it normally transfers data from upstream (write), rebuffering as > necessary if there is nothing else to send. >> >>> >>> In my opinion, it's not really worth to put much work on using the current >>> alsa plugin. As long as it works, don't touch it... until it get's fixed >>> in a proper way, possibly by using a pulse plugin instead. >> It is worth it. Alsa will be around for a long time. This is an opportunity >> for Ekiga people to contribute back to ptlib&opal (libraries that are >> crucial to this project) > OK, unless you provoke you don't get an answer... I actually share your > opinion :-) >> >>> As for the latency discussion about alsa vs pulse: This review shows that >>> anything will be much better than current alsa code... >> The current alsa code works mostly.. it is close.. If there was some usable >> docs at alsa to explain what is not good, that would help. >> Anyone able to work out what is actually wrong in the alsa plugin? > But we have 100 ms of hw buffer, roughly twice the size of other VOIP > applications. There are open issues about the overall design, threads, > objects etc. There are no quality metrics, we have no idea about things like > bytes transferred, hard errors, soft errors, buffer usage etc. And Andreas' > logs shows that the driver does not deliver data as expected. I don't want > to blame anyone or so, but I think we must face the fact that there *are* > problems, some of them requiring more than a point fix. > > As I said, take a look at the bug, there are some more details, despite the > horrible formatting. And bear in mind that I'm certainly wrong from time to > time. And that English isn't my native language, the nuances are a bit bit, > well, rough now and then :-) >> >> Derek. > --alec > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > > -- Derek Smithies Ph.D. IndraNet Technologies Ltd. Email: derek at indranet.co.nz ph +64 3 365 6485 Web: http://www.indranet-technologies.com/ From Eugen.Dedu at pu-pm.univ-fcomte.fr Tue Feb 24 20:56:25 2009 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Tue, 24 Feb 2009 21:56:25 +0100 Subject: [Ekiga-list] ekiga on Slackware 12.2 not working usefully... any suggestions? In-Reply-To: <20090224201350.GA4297@jdiamond-nb> References: <20090224201350.GA4297@jdiamond-nb> Message-ID: <49A45EF9.5080901@pu-pm.univ-fcomte.fr> Jim Diamond wrote: > Hi > > I have recently tried > ekiga 3.0.1 + opal 3.4.3 + ptlib 2.4.3 > ekiga 3.0.2 + opal 3.4.4 + ptlib 2.4.4 > ekiga 3.1.0 + opal 3.6.0 + ptlib 2.6.0 > under Slackware 12.2 (various computers, various kernels). > > 3.1.0 doesn't let me use my Logitech QuickCam Pro for Notebooks > (uvcvideo, needs V4L2 to work at all on my systems), so I gave up on > that. If I understand correctly, this webcam does not work on 3.1.0, but works on previous releases? Also, do you mean 3.1.1 (SVN trunk) or 3.1.0? > The other two versions seem to behave similarly with respect to these > problems: > > (1) The call recipient sees only his own video, the video of the caller > is never visible. > > (2) If the caller is viewing his own video before making a call, when > the call is established, he (apparently) alternately sees his own > video frames and frames of the call recipient. In other words, > the video picture is pretty much useless. > If the two video resolutions are not the same, the (whole) window > changes size with (apparently) each frame change, which adds to > the annoyance. > > If the caller was not looking at his own video, he sees the call > recipient's video fine. Could you check if you are hit by http://wiki.ekiga.org/index.php/Troubleshooting#I_hear_the_ring.2C_but_the_communication_is_not_established ? > This is pretty much a show stopper, so the fact that many people are > happily using ekiga suggest to me that it must be "me", but I have no > idea what I'm doing wrong. Older versions of ekiga worked fine for me > on older versions of Slackware. There are many, many different issues which might appear... -- Eugen From JDiamond at acadiau.ca Tue Feb 24 23:11:07 2009 From: JDiamond at acadiau.ca (Jim Diamond) Date: Tue, 24 Feb 2009 19:11:07 -0400 Subject: [Ekiga-list] ekiga on Slackware 12.2 not working usefully... any suggestions? In-Reply-To: <49A45EF9.5080901@pu-pm.univ-fcomte.fr> References: <20090224201350.GA4297@jdiamond-nb> <49A45EF9.5080901@pu-pm.univ-fcomte.fr> Message-ID: <20090224231107.GB4782@jdiamond-nb> On Tue, Feb 24, 2009 at 21:56 (+0100), Eugen Dedu wrote: > Jim Diamond wrote: >> Hi >> I have recently tried >> ekiga 3.0.1 + opal 3.4.3 + ptlib 2.4.3 >> ekiga 3.0.2 + opal 3.4.4 + ptlib 2.4.4 >> ekiga 3.1.0 + opal 3.6.0 + ptlib 2.6.0 >> under Slackware 12.2 (various computers, various kernels). >> 3.1.0 doesn't let me use my Logitech QuickCam Pro for Notebooks >> (uvcvideo, needs V4L2 to work at all on my systems), so I gave up on >> that. > If I understand correctly, this webcam does not work on 3.1.0, but works > on previous releases? Exactly. In 3.1.0 the only choice in my video device list pairs this camera up with V4L, not V4L2, and it doesn't work in that situation. > Also, do you mean 3.1.1 (SVN trunk) or 3.1.0? 3.1.0, as found via http://blog.ekiga.net/?p=112 which points me to ftp://ftp.gnome.org/pub/gnome/sources/ekiga/3.1 >> The other two versions seem to behave similarly with respect to these >> problems: >> (1) The call recipient sees only his own video, the video of the caller >> is never visible. >> (2) If the caller is viewing his own video before making a call, when >> the call is established, he (apparently) alternately sees his own >> video frames and frames of the call recipient. In other words, >> the video picture is pretty much useless. >> If the two video resolutions are not the same, the (whole) window >> changes size with (apparently) each frame change, which adds to >> the annoyance. >> If the caller was not looking at his own video, he sees the call >> recipient's video fine. > Could you check if you are hit by > http://wiki.ekiga.org/index.php/Troubleshooting#I_hear_the_ring.2C_but_the_communication_is_not_established > ? The communication is established, but the video only goes one way. >> This is pretty much a show stopper, so the fact that many people are >> happily using ekiga suggest to me that it must be "me", but I have no >> idea what I'm doing wrong. Older versions of ekiga worked fine for me >> on older versions of Slackware. > There are many, many different issues which might appear... Indeed, I can appreciate the difficulty. I'm hoping this report might trigger a synapse in someone's brain, and we could go from there. Cheers. Jim From jpuydt at free.fr Wed Feb 25 07:44:17 2009 From: jpuydt at free.fr (Julien Puydt) Date: Wed, 25 Feb 2009 08:44:17 +0100 Subject: [Ekiga-list] ekiga on Slackware 12.2 not working usefully... any suggestions? In-Reply-To: <20090224231107.GB4782@jdiamond-nb> References: <20090224201350.GA4297@jdiamond-nb> <49A45EF9.5080901@pu-pm.univ-fcomte.fr> <20090224231107.GB4782@jdiamond-nb> Message-ID: <49A4F6D1.1030805@free.fr> Jim Diamond a ?crit : > On Tue, Feb 24, 2009 at 21:56 (+0100), Eugen Dedu wrote: >> If I understand correctly, this webcam does not work on 3.1.0, but works >> on previous releases? > > Exactly. In 3.1.0 the only choice in my video device list pairs this > camera up with V4L, not V4L2, and it doesn't work in that situation. May I suggest that you install the ptlib v4l2 plugin? Snark on #ekiga From leamas.alec at gmail.com Wed Feb 25 08:07:51 2009 From: leamas.alec at gmail.com (Alec Leamas) Date: Wed, 25 Feb 2009 09:07:51 +0100 Subject: [Ekiga-list] PTLIB alsa plugin status In-Reply-To: References: <49A3BA0B.3010805@gmail.com> <49A3C7DF.1060400@gmail.com> Message-ID: <49A4FC57.1050104@gmail.com> Derek Smithies wrote: > Hi, > >>> - Playback and record thread are synchronized in a way that > forces the two >>>> streams to wait for each others I/O operations. >>> Yes - can someone test that ptlib alsa plugin works ok with this >>> mutex removed?? > This mutex is important, and should not syncrhonize the play&record > threads. > > There are two PSoundChannel class instances active during a call. > One for play. > One for record. > > These PSoundChannel class instances are seperate, and have seperately > opened connections to the sound_alsa plugin. Consequently, the mutex > you refer to is not syncrhonising access to play&record. > > The mutex is locking access to play variables (device pointers) + play > > A different mutex instance is locking access to write variables > (device pointers) + write. > > ================== > > Now, if the same PSoundChannel instance is used for play and record - > (which can be achieved by bad application writing) then you have an > application coding problem. I assume Ekiga does not have this issue. > > > ========================================= Hi :-) Thanks for this info! As you state, this should work as long as they are instantiated in a proper way. And it's simple just to add some assertions to make sure that this is indeed the case. I still don't get why the device pointers needs locking. Is the overall Ekiga design such as there are several threads writing concurrently? Or is this a general requirement for the driver, for other scenarios the Ekiga? In other words , is the PTlib alsa driver defined as reentrant? --a From Jim.Diamond at acadiau.ca Wed Feb 25 15:50:05 2009 From: Jim.Diamond at acadiau.ca (Jim Diamond) Date: Wed, 25 Feb 2009 11:50:05 -0400 Subject: [Ekiga-list] ekiga on Slackware 12.2 not working usefully... any suggestions? Message-ID: <20090225155005.GA16493@tux.acadiau.ca> On Wed, Feb 25, 2009 at 08:44 (+0100), Julien Puydt wrote: > Jim Diamond a ?crit : >> On Tue, Feb 24, 2009 at 21:56 (+0100), Eugen Dedu wrote: >>> If I understand correctly, this webcam does not work on 3.1.0, but >>> works on previous releases? >> Exactly. In 3.1.0 the only choice in my video device list pairs this >> camera up with V4L, not V4L2, and it doesn't work in that situation. > May I suggest that you install the ptlib v4l2 plugin? Do you mean /usr/lib/ptlib-2.4.4/devices/videoinput/v4l2_pwplugin.so ? If so, it is there. If not, can you tell me more about what you mean? Thanks. Jim From dsandras at seconix.com Wed Feb 25 16:50:35 2009 From: dsandras at seconix.com (Damien Sandras) Date: Wed, 25 Feb 2009 17:50:35 +0100 Subject: [Ekiga-list] ekiga on Slackware 12.2 not working usefully... any suggestions? In-Reply-To: <20090225155005.GA16493@tux.acadiau.ca> References: <20090225155005.GA16493@tux.acadiau.ca> Message-ID: <1235580635.5512.26.camel@scorpion.multitel.be> Le mercredi 25 f?vrier 2009 ? 11:50 -0400, Jim Diamond a ?crit : > On Wed, Feb 25, 2009 at 08:44 (+0100), Julien Puydt wrote: > > > Jim Diamond a ?crit : > >> On Tue, Feb 24, 2009 at 21:56 (+0100), Eugen Dedu wrote: > >>> If I understand correctly, this webcam does not work on 3.1.0, but > >>> works on previous releases? > > >> Exactly. In 3.1.0 the only choice in my video device list pairs this > >> camera up with V4L, not V4L2, and it doesn't work in that situation. > > > May I suggest that you install the ptlib v4l2 plugin? > > Do you mean /usr/lib/ptlib-2.4.4/devices/videoinput/v4l2_pwplugin.so ? > If so, it is there. > > If not, can you tell me more about what you mean? 3.1.0 does not use ptlib 2.4.4 but a more recent version. Wouldn't you be mixing things up? Damien From hs.samix at gmail.com Wed Feb 25 16:51:10 2009 From: hs.samix at gmail.com (H. S.) Date: Wed, 25 Feb 2009 11:51:10 -0500 Subject: [Ekiga-list] ekiga beginner questions Message-ID: Hello, I have an Ekiga account but haven't used it much so far. I use Ekiga on Debian Testing and Unstable. I plan to ask some of my friends and relatives to get Ekiga account too. They use Windows XP and Ubuntu (Hardy, Intrepid). So far the above contacts have been using Skype and Yahoo Messenger. With this background, I have a few questions regarding Ekiga. 1. Does it support encryption? From google search it appears like it was supposed to from 3.0 onwards. 2. Does it support photo sharing (like in Yahoo Messenger). Not a deal breaker but it would go a long in shifting people who use Yahoo Messenger completely to Ekiga if it did. If it does not at present, any future plans? 3. It is any more difficult to setup and use than Skype through consumer router or modem (NAT)? I have no problem configuring my router machine (which runs iptables) for this, but I do not want to put other users in this situation. 4. Can it be used on Linux (Debian, Ubuntu), Windows and also on Mac OSX? Thanks. Regards. -------------- next part -------------- An HTML attachment was scrubbed... URL: From dsandras at seconix.com Wed Feb 25 16:51:08 2009 From: dsandras at seconix.com (Damien Sandras) Date: Wed, 25 Feb 2009 17:51:08 +0100 Subject: [Ekiga-list] Newbie with questions... In-Reply-To: References: <49A31CC7.8040804@pu-pm.univ-fcomte.fr> <1235465349.3951.8.camel@scorpion.multitel.be> Message-ID: <1235580668.5512.28.camel@scorpion.multitel.be> Le mardi 24 f?vrier 2009 ? 10:18 -0600, Reed, Gene R[EQ] a ?crit : > I ran the command as you suggested, and I have upgraded to Ekiga v3.0.2. Results when I enable my account via account settings, "Could not register(Forbidden)". Any suggestions you may have would be appreciated. > Impossible to tell without a full debug output, but it would seem your password/username are not correct/accepted. Damien From dsandras at seconix.com Wed Feb 25 16:55:16 2009 From: dsandras at seconix.com (Damien Sandras) Date: Wed, 25 Feb 2009 17:55:16 +0100 Subject: [Ekiga-list] ekiga beginner questions In-Reply-To: References: Message-ID: <1235580916.5512.31.camel@scorpion.multitel.be> Le mercredi 25 f?vrier 2009 ? 11:51 -0500, H. S. a ?crit : > Hello, > > I have an Ekiga account but haven't used it much so far. I use Ekiga > on Debian Testing and Unstable. I plan to ask some of my friends and > relatives to get Ekiga account too. They use Windows XP and Ubuntu > (Hardy, Intrepid). > > So far the above contacts have been using Skype and Yahoo Messenger. > With this background, I have a few questions regarding Ekiga. > > 1. Does it support encryption? From google search it appears like it > was supposed to from 3.0 onwards. > not yet. > 2. Does it support photo sharing (like in Yahoo Messenger). Not a deal > breaker but it would go a long in shifting people who use Yahoo > Messenger completely to Ekiga if it did. If it does not at present, > any future plans? I don't think it is planned (currently). > 3. It is any more difficult to setup and use than Skype through > consumer router or modem (NAT)? I have no problem configuring my > router machine (which runs iptables) for this, but I do not want to > put other users in this situation. It depends, sometimes, it is more difficult, but in 90% of the cases, it will run well. Either because the router supports SIP or because STUN works. > 4. Can it be used on Linux (Debian, Ubuntu), Windows and also on Mac > OSX? Not Mac OSX. Damien From hs.samix at gmail.com Wed Feb 25 17:03:21 2009 From: hs.samix at gmail.com (H. S.) Date: Wed, 25 Feb 2009 12:03:21 -0500 Subject: [Ekiga-list] ekiga beginner questions In-Reply-To: <1235580916.5512.31.camel@scorpion.multitel.be> References: <1235580916.5512.31.camel@scorpion.multitel.be> Message-ID: On Wed, Feb 25, 2009 at 11:55 AM, Damien Sandras wrote: > Le mercredi 25 f?vrier 2009 ? 11:51 -0500, H. S. a ?crit : > > > > 1. Does it support encryption? From google search it appears like it > > was supposed to from 3.0 onwards. > > > > not yet. ETA? > > > > 3. It is any more difficult to setup and use than Skype through > > consumer router or modem (NAT)? I have no problem configuring my > > router machine (which runs iptables) for this, but I do not want to > > put other users in this situation. > > It depends, sometimes, it is more difficult, but in 90% of the cases, it > will run well. Either because the router supports SIP or because STUN > works. > Anything special about those 10% cases where it does not work? Just trying to get a clear picture here and perhaps avoid problems, or at least minimize them. > > > 4. Can it be used on Linux (Debian, Ubuntu), Windows and also on Mac > > OSX? > > Not Mac OSX. > Any alternative? Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jim.Diamond at acadiau.ca Wed Feb 25 17:13:24 2009 From: Jim.Diamond at acadiau.ca (Jim Diamond) Date: Wed, 25 Feb 2009 13:13:24 -0400 Subject: [Ekiga-list] ekiga on Slackware 12.2 not working usefully... any suggestions? In-Reply-To: <1235580635.5512.26.camel@scorpion.multitel.be> References: <20090225155005.GA16493@tux.acadiau.ca> <1235580635.5512.26.camel@scorpion.multitel.be> Message-ID: <20090225171324.GA17093@tux.acadiau.ca> On Wed, Feb 25, 2009 at 17:50 (+0100), Damien Sandras wrote: > Le mercredi 25 f?vrier 2009 ? 11:50 -0400, Jim Diamond a ?crit : >> On Wed, Feb 25, 2009 at 08:44 (+0100), Julien Puydt wrote: >>> Jim Diamond a ?crit : >>>> On Tue, Feb 24, 2009 at 21:56 (+0100), Eugen Dedu wrote: >>>>> If I understand correctly, this webcam does not work on 3.1.0, but >>>>> works on previous releases? >>>> Exactly. In 3.1.0 the only choice in my video device list pairs this >>>> camera up with V4L, not V4L2, and it doesn't work in that situation. >>> May I suggest that you install the ptlib v4l2 plugin? >> Do you mean /usr/lib/ptlib-2.4.4/devices/videoinput/v4l2_pwplugin.so ? >> If so, it is there. >> If not, can you tell me more about what you mean? > 3.1.0 does not use ptlib 2.4.4 but a more recent version. Wouldn't you > be mixing things up? I would be if I tried those two at the same time :-) In my original message, I wrote > I have recently tried > ekiga 3.0.1 + opal 3.4.3 + ptlib 2.4.3 > ekiga 3.0.2 + opal 3.4.4 + ptlib 2.4.4 > ekiga 3.1.0 + opal 3.6.0 + ptlib 2.6.0 > under Slackware 12.2 (various computers, various kernels). > > 3.1.0 doesn't let me use my Logitech QuickCam Pro for Notebooks > (uvcvideo, needs V4L2 to work at all on my systems), so I gave up on > that. so I assumed Julien's question was about 3.0.2. However, now that you ask this question, I see that for whatever reason (I used the same configure options for 3.1.0 as for 3.0.2, which did build the V4L2 plugin), I did not build the V4L2 plugin for 3.1.0. I'll give that a try, just in case 3.1.0 solves my real problem. Jim From palos at post.sk Wed Feb 25 18:13:45 2009 From: palos at post.sk (Palo S.) Date: 25 Feb 2009 19:13:45 +0100 (CET) Subject: [Ekiga-list] ekiga on Slackware 12.2 not working usefully... anysuggestions? Message-ID: <49A58A59.000002.11639@kamasutra> > > (1) The call recipient sees only his own video, the video of the caller > is never visible. Which video codec are you using? I have similar problem with Theora codec: the caller only sees his own video, the recipient sees both. With H.264 it works ok, except that the remote video only appears after approx. 20 sec of call and that H.264 is randomly disabled by Ekiga at startup. I don\'t have any issues only with H.261. Have you tried changing the video codec? P. __________ http://www.tahaj.sk - Najnavstevovanejsia stranka slovenskeho downloadu From Jim.Diamond at acadiau.ca Wed Feb 25 18:36:50 2009 From: Jim.Diamond at acadiau.ca (Jim Diamond) Date: Wed, 25 Feb 2009 14:36:50 -0400 Subject: [Ekiga-list] ekiga on Slackware 12.2 not working usefully... anysuggestions? In-Reply-To: <49A58A59.000002.11639@kamasutra> References: <49A58A59.000002.11639@kamasutra> Message-ID: <20090225183650.GA17419@tux.acadiau.ca> On Wed, Feb 25, 2009 at 19:13 (+0100), Palo S. wrote: >> (1) The call recipient sees only his own video, the video of the >> caller is never visible. > Which video codec are you using? I have similar problem > with Theora codec: the caller only sees his own video, > the recipient sees both. With H.264 it works ok, except > that the remote video only appears after approx. 20 sec > of call and that H.264 is randomly disabled by Ekiga at > startup. I don\'t have any issues only with H.261. Have > you tried changing the video codec? Well, in the "misery loves company" arena, I'm glad to see I'm not the only one seeing this. I had tried turning off theora with 3.0.1, but had not tried it with 3.0.2. With 3.0.2 I continue to see the problem with both ends using H.261. Thanks for the suggestion. If I get 3.1.0 working I'll try it there. Jim From dsandras at seconix.com Wed Feb 25 18:44:23 2009 From: dsandras at seconix.com (Damien Sandras) Date: Wed, 25 Feb 2009 19:44:23 +0100 Subject: [Ekiga-list] ekiga beginner questions In-Reply-To: References: <1235580916.5512.31.camel@scorpion.multitel.be> Message-ID: <1235587463.3978.3.camel@scorpion.multitel.be> Le mercredi 25 f?vrier 2009 ? 12:03 -0500, H. S. a ?crit : > > > not yet. > > ETA? When it's ready. Most contributors only code in their spare time, my spare time is really scarce nowadays, so I prefer not doing any promise. > It depends, sometimes, it is more difficult, but in 90% of the > cases, it > will run well. Either because the router supports SIP or > because STUN > works. > > > > Anything special about those 10% cases where it does not work? Just > trying to get a clear picture here and perhaps avoid problems, or at > least minimize them. See wiki.ekiga.org, in those cases, a simple port forwarding is enough. > > > 4. Can it be used on Linux (Debian, Ubuntu), Windows and > also on Mac > > OSX? > > > Not Mac OSX. > > Any alternative? > Any SIP software will work. But I'm not familiar with OS X. Perhaps SJPhone will work. Damien From hs.samix at gmail.com Wed Feb 25 18:48:51 2009 From: hs.samix at gmail.com (H. S.) Date: Wed, 25 Feb 2009 13:48:51 -0500 Subject: [Ekiga-list] ekiga beginner questions In-Reply-To: <1235587463.3978.3.camel@scorpion.multitel.be> References: <1235580916.5512.31.camel@scorpion.multitel.be> <1235587463.3978.3.camel@scorpion.multitel.be> Message-ID: On Wed, Feb 25, 2009 at 1:44 PM, Damien Sandras wrote: > Le mercredi 25 f?vrier 2009 ? 12:03 -0500, H. S. a ?crit : > > > > > > not yet. > > > > ETA? > > When it's ready. Most contributors only code in their spare time, my > spare time is really scarce nowadays, so I prefer not doing any promise. > > > > It depends, sometimes, it is more difficult, but in 90% of the > > cases, it > > will run well. Either because the router supports SIP or > > because STUN > > works. > > > > > > > > Anything special about those 10% cases where it does not work? Just > > trying to get a clear picture here and perhaps avoid problems, or at > > least minimize them. > > See wiki.ekiga.org, in those cases, a simple port forwarding is enough. > > > > > > 4. Can it be used on Linux (Debian, Ubuntu), Windows and > > also on Mac > > > OSX? > > > > > > Not Mac OSX. > > > > Any alternative? > > > > Any SIP software will work. But I'm not familiar with OS X. Perhaps > SJPhone will work. > > Damien > > Thanks for your comments and feedback. Much appreciated. Regards. -------------- next part -------------- An HTML attachment was scrubbed... URL: From palos at post.sk Wed Feb 25 18:58:39 2009 From: palos at post.sk (Palo S.) Date: 25 Feb 2009 19:58:39 +0100 (CET) Subject: [Ekiga-list] ekiga beginner questions Message-ID: <49A594DF.000003.16725@kamasutra> > Anything special about those 10% cases where it does not work? Just trying > to get a clear picture here and perhaps avoid problems, or at least minimize > them. symmetric NAT, broken router SIP support, port forwarding conflicts... > > > > > 4. Can it be used on Linux (Debian, Ubuntu), Windows and also on Mac > > > OSX? > > > > Not Mac OSX. > > > > Any alternative? Any SIP client for voice talks. Check out this page for other functionalities: http://wiki.ekiga.org/index.php/Which_programs_work_with_Ekiga_%3F#Mac_OS Also note that (as far as I know) Ekiga for Windows is still beta. Based on my experiences, Ekiga is a great piece of software but it is not prepared to replace Skype/ Yahoo Mess on a larger scale mainly due to NAT issues, poor non-Linux platform support + some long-term video and presence related problems. P. __________ http://sport.sme.sk - Najkomplexnej?ie inform?cie zo ?portu From mtbc at ixod.org Wed Feb 25 19:03:49 2009 From: mtbc at ixod.org (Mark T.B. Carroll) Date: Wed, 25 Feb 2009 14:03:49 -0500 Subject: [Ekiga-list] ekiga beginner questions In-Reply-To: <49A594DF.000003.16725@kamasutra> (Palo S.'s message of "25 Feb 2009 19\:58\:39 +0100 \(CET\)") References: <49A594DF.000003.16725@kamasutra> Message-ID: <87iqmy8hka.fsf@ixod.org> Palo S. writes: >> Anything special about those 10% cases where it does not work? Just trying >> to get a clear picture here and perhaps avoid problems, or at least minimize >> them. > > symmetric NAT, broken router SIP support, port forwarding > conflicts... I've been fascinated that since forwarding UDP 5060-5100 at my router to the machine I use Ekiga from, my separate Broadvoice SIP phone (behind the same NAT) still works okay - netstat-nat is currently reporting, udp broadvoice.mtbc.internal:sip 147.135.32.222:sip ASSURED I wonder how they do it. The Broadvoice box /stops/ working if I turn on the Linux 2.6 CONFIG_NF_NAT_SIP kernel option on the router, though I wondered if that option would help Ekiga or not. Mark From michel.memeteau at gmail.com Wed Feb 25 20:30:33 2009 From: michel.memeteau at gmail.com (michel memeteau) Date: Wed, 25 Feb 2009 21:30:33 +0100 Subject: [Ekiga-list] ekiga beginner questions In-Reply-To: <1235587463.3978.3.camel@scorpion.multitel.be> References: <1235580916.5512.31.camel@scorpion.multitel.be> <1235587463.3978.3.camel@scorpion.multitel.be> Message-ID: On Wed, Feb 25, 2009 at 7:44 PM, Damien Sandras wrote: > > > Anything special about those 10% cases where it does not work? Just > > trying to get a clear picture here and perhaps avoid problems, or at > > least minimize them. > > See wiki.ekiga.org, in those cases, a simple port forwarding is enough. > Symmetric Nat is really Frequent in French DSL ISP modems ( Freebox and neufBox I think ) , and as long as TURN ICE or Upnp support Won't be in Ekiga , port forwarding will still be needed in a lot of cases which leads usually to not recommends Ekiga to your granMother ( a Pity ) > > > Not Mac OSX. > > > > Any alternative? > > > Any SIP software will work. But I'm not familiar with OS X. Perhaps > SJPhone will work. > Xmeeting is definitly the best option for me , I use the lastest 0.4alpha2 regularly without any problems with H263 (No H264 though) -- %<------------------------------------------------------->% 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 Eugen.Dedu at pu-pm.univ-fcomte.fr Wed Feb 25 20:53:53 2009 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Wed, 25 Feb 2009 21:53:53 +0100 Subject: [Ekiga-list] ekiga beginner questions In-Reply-To: References: <1235580916.5512.31.camel@scorpion.multitel.be> Message-ID: <49A5AFE1.1010700@pu-pm.univ-fcomte.fr> H. S. wrote: > On Wed, Feb 25, 2009 at 11:55 AM, Damien Sandras wrote: > >> Le mercredi 25 f?vrier 2009 ? 11:51 -0500, H. S. a ?crit : >>> 4. Can it be used on Linux (Debian, Ubuntu), Windows and also on Mac >>> OSX? >> Not Mac OSX. >> > > Any alternative? See http://wiki.ekiga.org/index.php/SipFacile -- Eugen From Eugen.Dedu at pu-pm.univ-fcomte.fr Wed Feb 25 21:09:15 2009 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Wed, 25 Feb 2009 22:09:15 +0100 Subject: [Ekiga-list] News on debian snapshots Message-ID: <49A5B37B.5040003@pu-pm.univ-fcomte.fr> Hi all, News on debian snapshots, starting from this night: * ekiga is now built with gstreamer support (Julien Puydt would be grateful if you can test it, even if there are some known problems). * The AVC plugin is not compiled anymore (the package is still there, but will be removed soon). Please tell if you really need it. It seems to me that ptlib needs libraw1394-dev v1, but v1 is not available anymore on debian unstable and very soon in testing either. Here is the error I receive with v2 installed: make[3]: Entering directory `/home/dedu/softs/ekiga/ptlib2/plugins/vidinput_avc' mkdir -p /home/dedu/softs/ekiga/ptlib2/lib_linux_x86_64/device/videoinput g++ -DPTRACING=1 -D_REENTRANT -D_GNU_SOURCE=1 -D_REENTRANT -I/usr/include/SDL -fno-exceptions -Wall -DP_64BIT -fPIC -DPIC -DNDEBUG -Os -fPIC -I/home/dedu/softs/ekiga/ptlib2/include \ -L/home/dedu/softs/ekiga/ptlib2/lib_linux_x86_64 \ -I. -shared vidinput_avc.cxx \ -L/home/dedu/softs/ekiga/ptlib2/lib_linux_x86_64 -lraw1394 -ldv -lrom1394 \ -o /home/dedu/softs/ekiga/ptlib2/lib_linux_x86_64/device/videoinput/avc_pwplugin.so vidinput_avc.cxx: In member function ?virtual PBoolean PVideoInputDevice_1394AVC::Start()?: vidinput_avc.cxx:166: error: ?raw1394_set_iso_handler? was not declared in this scope vidinput_avc.cxx: In member function ?virtual PBoolean PVideoInputDevice_1394AVC::GetFrameDataNoDelay(BYTE*, PINDEX*)?: vidinput_avc.cxx:374: error: ?raw1394_start_iso_rcv? was not declared in this scope vidinput_avc.cxx:418: error: ?raw1394_stop_iso_rcv? was not declared in this scope make[3]: *** [/home/dedu/softs/ekiga/ptlib2/lib_linux_x86_64/device/videoinput/avc_pwplugin.so] Error 1 make[3]: Leaving directory `/home/dedu/softs/ekiga/ptlib2/plugins/vidinput_avc' make[2]: *** [optshared] Error 2 * dbus support is still disabled as for now. Please tell me if you need it. * gnome-config-tool needs a bit updated. Cheers, -- Eugen From derek at indranet.co.nz Wed Feb 25 21:28:30 2009 From: derek at indranet.co.nz (Derek Smithies) Date: Thu, 26 Feb 2009 10:28:30 +1300 (NZDT) Subject: [Ekiga-list] PTLIB alsa plugin status In-Reply-To: <49A4FC57.1050104@gmail.com> References: <49A3BA0B.3010805@gmail.com> <49A3C7DF.1060400@gmail.com> <49A4FC57.1050104@gmail.com> Message-ID: Hi, On Wed, 25 Feb 2009, Alec Leamas wrote: > Hi :-) > > Thanks for this info! As you state, this should work as long as they are > instantiated in a proper way. And it's simple just to add some assertions to > make sure that this is indeed the case. > > I still don't get why the device pointers needs locking. Is the overall Ekiga > design such as there are several threads writing concurrently? Or is this a > general requirement for the driver, for other scenarios the Ekiga? In other > words , is the PTlib alsa driver defined as reentrant? > yes, the ptlib alsa driver needs to be reentrant. One thread could attempt to close the audio device while a second thread is reading/writing data from/to the alsa system. It is not the overall Ekiga design that sets the requirment for coping with multiple threads - it is a the PTLib/OPAL design that sets the requirement for coping with multiple threads. The discussion topic of threads and too many threads and so on has occuppied many hours at conferences, and many emails, and is slightly tedious. A useful article on threads is found at: http://www.gotw.ca/publications/concurrency-ddj.htm In my view, the reason many programmers argue vehemently against threads is a combination of several factors *all their early programs were single threaded (e.g. hello_world) and so they developed the mindset of only knowing how to cope with 1 thread. *some programming styles (which are spaghetti like in nature) are torture to debug when threaded *many of the open source tools (in particular debuggers) don't handle threads well and make the whole code&fix process too hard However, ptlib and opal are coded to a high degree of quality. There are still issues (device plugins) but these are getting fewer and fewer. Given the nature of voip and how voip works, I don't think any other model would work. Remember that opal is a library, and is used by people making hundreds of simultaneous calls. If you do propose a different way of doing things, will the new architecture cope with being scaled up? Derek. -- Derek Smithies Ph.D. IndraNet Technologies Ltd. Email: derek at indranet.co.nz ph +64 3 365 6485 Web: http://www.indranet-technologies.com/ From leamas.alec at gmail.com Wed Feb 25 23:05:38 2009 From: leamas.alec at gmail.com (Alec Leamas) Date: Thu, 26 Feb 2009 00:05:38 +0100 Subject: [Ekiga-list] PTLIB alsa plugin status In-Reply-To: References: <49A3BA0B.3010805@gmail.com> <49A3C7DF.1060400@gmail.com> <49A4FC57.1050104@gmail.com> Message-ID: <49A5CEC2.6090206@gmail.com> Derek Smithies wrote: > Hi, > On Wed, 25 Feb 2009, Alec Leamas wrote: >> Hi :-) >> >> Thanks for this info! As you state, this should work as long as >> they are instantiated in a proper way. And it's simple just to add >> some assertions to make sure that this is indeed the case. >> >> I still don't get why the device pointers needs locking. Is the >> overall Ekiga design such as there are several threads writing >> concurrently? Or is this a general requirement for the driver, for >> other scenarios the Ekiga? In other words , is the PTlib alsa driver >> defined as reentrant? >> > yes, the ptlib alsa driver needs to be reentrant. > > One thread could attempt to close the audio device while a second > thread is reading/writing data from/to the alsa system. > > It is not the overall Ekiga design that sets the requirment for coping > with multiple threads - it is a the PTLib/OPAL design that sets the > requirement for coping with multiple threads. > > The discussion topic of threads and too many threads and so on has > occuppied many hours at conferences, and many emails, and is slightly > tedious. A useful article on threads is found at: > http://www.gotw.ca/publications/concurrency-ddj.htm > > In my view, the reason many programmers argue vehemently against > threads is a combination of several factors > *all their early programs were single threaded (e.g. hello_world) and so > they developed the mindset of only knowing how to cope with 1 thread. > *some programming styles (which are spaghetti like in nature) are > torture > to debug when threaded > *many of the open source tools (in particular debuggers) don't handle > threads well and make the whole code&fix process too hard > > However, ptlib and opal are coded to a high degree of quality. There > are still issues (device plugins) but these are getting fewer and > fewer. Given the nature of voip and how voip works, I don't think any > other model would work. > Remember that opal is a library, and is used by people making > hundreds of simultaneous calls. If you do propose a different way of > doing things, will Hey! Have I said it's something wrong with threads? I have actually my background in tecknical systems, I was using threads long time before the word was used :-) I was just raising a question, and you have answered it. The PTlib alsa driver is defined as reentrant. I have no problems with this, once I understand it (it might be useful to document this fact in the PSoundChannel interface, I doubt I'm the only one which will stumble into this). But there *are* problems. A well behaved alsa driver should work better aganist pulse, other does. The hw buffer is way to large, 100 ms latency instead of ~50. No statistics. No rebuffering. But you have convinced on one, important point: it should be possible to enhance the driver with a set of smaller patches instead of a major rewrite. Such things are always easier. And I have absolutely no intention to look under the hood in the opal framwork. I just found Andreas' posting, and realized that I had some odd experience in alsa which might be useful. And after looking into this, I still feel that a better alsa interface in Ekiga is really important to get better latency and quality, both of which are crucial in a voip context. Or? BTW, are you the one which have an overall understanding the complete buffering scheme in Ekiga? --a From leamas.alec at gmail.com Wed Feb 25 23:20:09 2009 From: leamas.alec at gmail.com (Alec Leamas) Date: Thu, 26 Feb 2009 00:20:09 +0100 Subject: [Ekiga-list] A comparison ALSA-PULSE (long, addendum) In-Reply-To: <49A3CD1D.5040703@postincrement.com> References: <49A11F5A.7090908@gmail.com> <49A28E4A.2090007@gmail.com> <49A31251.3050103@gmail.com> <874oyk7stn.fsf@ixod.org> <49A31764.1070808@gmail.com> <49A3CD1D.5040703@postincrement.com> Message-ID: <49A5D229.3070400@gmail.com> Hi! I'm a newbie here, and shouldn't really answer... but since nobody else does, I can share my thoughts. Which basically are that this looks fine, the Ekiga people focus on enhancing the alsa driver, you handle the new pulse plugin which obviously is needed. But let's hope someone of the elderly let us know what they think. I presume you already have thought of this, but just in case... a few things I think would be nice in a new plugin interface: - Event-driven model with callbacks matching e. g., pulse as an alternative - A mechanism to retrieve statistics in a generic way from the connection. Craig Southeren wrote: > To all > > I have just noticed this thread. I wish someone had posted it on the > Opal list, where Robert and I might have noticed it earlier :) > > We are currently planning to add a new audio and video device plugin > interface to Opal. This new multimedia device interface will be > similar to the current codec API (allowing plugins to be written > without PTLib) and will support additional functionality such as: > > - support for devices that offer encoded media (such as pre-encoded > video) > > - support for devices that offer both audio and video. > > One of the first plugins I intend to write is a new Pulse audio > plugin, because Fedora uses pulseaudio by default, and I am sick of > audio not working without lots of changes :) > > I'd welcome comments from anyone on these plans > > Craig > > Derek Smithies wrote: >> Hi, >>>> Perhaps it's PTLib underneath it? I really don't know, I'm just >>>> throwing >>>> the idea out there! >> >> It is PTLib which contains the code to read from alsa. >> >> Surely, the ideal is not to go via ALSA, but have ptlib directly talk >> to pulse. Thus, we need to write a ptlib plugin for pulse audio. >> >> We know how ptlib plugins work. There are example plugins for alsa, >> esd, oss, sunaudio. The big question is writing a plugin for pulse. >> >> What is involved in writing code that talks directly to pulse ? >> Anyone know example code, or of the pulse api docs? >> >> Please don't refer me to docs which say "just use alsa code". We are >> using alsa code, and that is why we are having this issue. >> >> Derek. > > From Jim.Diamond at acadiau.ca Wed Feb 25 23:51:53 2009 From: Jim.Diamond at acadiau.ca (Jim Diamond) Date: Wed, 25 Feb 2009 19:51:53 -0400 Subject: [Ekiga-list] ekiga on Slackware 12.2 not working usefully... any suggestions? In-Reply-To: <49A4F6D1.1030805@free.fr> References: <20090224201350.GA4297@jdiamond-nb> <49A45EF9.5080901@pu-pm.univ-fcomte.fr> <20090224231107.GB4782@jdiamond-nb> <49A4F6D1.1030805@free.fr> Message-ID: <20090225235153.GA22390@jdiamond-nb> On Wed, Feb 25, 2009 at 08:44 (+0100), Julien Puydt wrote: > Jim Diamond a ?crit : >> On Tue, Feb 24, 2009 at 21:56 (+0100), Eugen Dedu wrote: >>> If I understand correctly, this webcam does not work on 3.1.0, but >>> works on previous releases? >> Exactly. In 3.1.0 the only choice in my video device list pairs this >> camera up with V4L, not V4L2, and it doesn't work in that situation. > May I suggest that you install the ptlib v4l2 plugin? OK, I compiled that plugin for 3.1.0 by installing a libv4l-0.5.7 package and then re-building ptlib-2.6.0. Now ekiga sees my camera. However (1) if it receives a call from an ekiga 3.0.1 or 3.1.0 system it seg faults and dies. It also makes the complaints ** (ekiga:22591): CRITICAL **: gm_conf_get_string: assertion `key /apps/ekiga/general/user_interface/main_window/size has no corresponding entry! ' failed ** (ekiga:22591): CRITICAL **: entry_get_bool: assertion `gmconf key /apps/ekiga/general/nat/disable_stun is of type GM_CONF_BOOL' failed I don't know if anyone who knows the code finds that particularly revealing. (2) If 3.1.0 places a call to a 3.0.1 system, it quickly shifts the video from the remote camera, the local camera, and the ekiga icon (i.e., what you see when not on a call if you are not displaying any video). This is similar to what I originally described, with the addition of the icon. Regrettably, 3.1.0 doesn't solve the problem, and, indeed, makes it a bit worse. I have to assume that there is some weird thing going on in my system that none/few of you see. Is there anyone here (besides me) else using it with --disable-gnome --disable-gconf Thanks for any suggestions anyone can provide. Jim From derek at indranet.co.nz Thu Feb 26 00:16:17 2009 From: derek at indranet.co.nz (Derek Smithies) Date: Thu, 26 Feb 2009 13:16:17 +1300 (NZDT) Subject: [Ekiga-list] PTLIB alsa plugin status In-Reply-To: <49A5CEC2.6090206@gmail.com> References: <49A3BA0B.3010805@gmail.com> <49A3C7DF.1060400@gmail.com> <49A4FC57.1050104@gmail.com> <49A5CEC2.6090206@gmail.com> Message-ID: On Thu, 26 Feb 2009, Alec Leamas wrote: > But there *are* problems. A well behaved alsa driver should work better > aganist pulse, other does. The hw buffer is way to large, 100 ms latency > instead of ~50. No statistics. No rebuffering. But you have convinced on > one, important point: it should be possible to enhance the driver with a set > of smaller patches instead of a major rewrite. Such things are always easier. > > And I have absolutely no intention to look under the hood in the opal > framwork. I just found Andreas' posting, and realized that I had some odd > experience in alsa which might be useful. And after looking into this, I > still feel that a better alsa interface in Ekiga is really important to get > better latency and quality, both of which are crucial in a voip context. Or? > > BTW, are you the one which have an overall understanding the complete > buffering scheme in Ekiga? I understand the ptlib and opal side of things quite well. I had a look at Ekiga, and read about the classes AudioInputCore and AudioInputManager. These Audio.... classes are necessary to deal with sound device insertion/deletion - such as inserting a USB headset. My first thought was that the OS (not the app) should deal with device insertion/deletion, but Alsa does not. Pulse is supposed to deal with sound device insertion/deletion. The ubuntu forums are full of people complaining about pulse. There is no buffering mechanism in Ekiga that I saw. Derek. -- Derek Smithies Ph.D. IndraNet Technologies Ltd. Email: derek at indranet.co.nz ph +64 3 365 6485 Web: http://www.indranet-technologies.com/ From mtbc at ixod.org Thu Feb 26 02:02:58 2009 From: mtbc at ixod.org (Mark T.B. Carroll) Date: Wed, 25 Feb 2009 21:02:58 -0500 Subject: [Ekiga-list] Incoming call failure with 3.1.1 In-Reply-To: <1235062650.23177.8.camel@scorpion.multitel.be> (Damien Sandras's message of "Thu\, 19 Feb 2009 17\:57\:30 +0100") References: <87iqn7t2io.fsf@ixod.org> <1235062650.23177.8.camel@scorpion.multitel.be> Message-ID: <87ab8aosz1.fsf@ixod.org> Damien Sandras writes: > Le jeudi 19 f?vrier 2009 ? 00:32 -0500, Mark T.B. Carroll a ?crit : >> I have run through the configuration assistant thing from start to >> finish. I can call the 500 at ekiga.net echo test and that works just fine. >> However, calling the 520 at ekiga.net callback service has it hang up on me >> and then ... nothing, though the -d 5 output shows that it is indeed >> getting a callback initiated from from sip:500 at ekiga.net which is then >> aborted. I am behind NAT and the router forwards incoming UDP from port >> 5060 to 5100 to the machine I'm using and acts as a gateway to let all >> my outgoing packets out. >> >> Should I gzip my -d 4 output and send it to somebody? I can also sniff >> packets and send pcap files. I use Debian; software versions are, > > There is a known problem with incoming calls and the current snapshot. I > will fix it this week-end. Now with the 20090225 one, the incoming call does arrive (yay!), I hit `accept', and it segfaults. I can still send my -d 4 output to somebody. (-: Mark From sstoedtgen at algol-europe.com Thu Feb 26 08:11:18 2009 From: sstoedtgen at algol-europe.com (Stefan Stoedtgen) Date: Thu, 26 Feb 2009 09:11:18 +0100 Subject: [Ekiga-list] WG: Connect to a LifeSize HD System Message-ID: Hi Ekiga List! I'm using Ekiga 3.0.2 stable under Windows XP, SP2 with a logitech QuickCam. I tried to connect to a LifeSize Room HD Conferencing Unit (www.lifesize.com) which uses SIP and H323 for communication. The connection seems to be established, but then, it breaks down. I attached you the error.log. Can you help me with this problem? Thanks for your Support! Gru?/Best regards , Stefan 2009/02/24 12:23:26.678 0:18.395 dialer:5520 OpalMan Set up call from pc:* to h323:fishtank.lifesize.com 2009/02/24 12:23:26.678 0:18.395 dialer:5520 Call Created Call[i27a0b1e11] 2009/02/24 12:23:26.678 0:18.395 dialer:5520 OpalMan Set up connection to "pc:*" 2009/02/24 12:23:26.678 0:18.396 dialer:5520 OpalCon Created connection Call[i27a0b1e11]-EP[1] 2009/02/24 12:23:26.678 0:18.396 dialer:5520 Silence Parameters set: mode=AdaptiveSilenceDetection, threshold=0, silencedb=3200, signaldb=80, period=4800 2009/02/24 12:23:26.678 0:18.396 dialer:5520 Silence Handler created 2009/02/24 12:23:26.678 0:18.396 dialer:5520 Echo Canceler Handler created 2009/02/24 12:23:26.678 0:18.396 dialer:5520 PCSS Created PC sound system connection with token '1' 2009/02/24 12:23:26.678 0:18.396 dialer:5520 OpalCon SetPhase from UninitialisedPhase to SetUpPhase for Call[i27a0b1e11]-EP[1] 2009/02/24 12:23:26.678 0:18.396 dialer:5520 OpalMan On incoming connection Call[i27a0b1e11]-EP[1] 2009/02/24 12:23:26.678 0:18.396 dialer:5520 Call GetOtherPartyConnection Call[i27a0b1e11]-EP[1] 2009/02/24 12:23:26.678 0:18.396 dialer:5520 OpalMan Searching for route "pc:sstoedtgen h323:fishtank.lifesize.com" 2009/02/24 12:23:26.678 0:18.396 dialer:5520 OpalMan Set up connection to "h323:fishtank.lifesize.com" 2009/02/24 12:23:26.678 0:18.396 dialer:5520 H323 Making call to: h323:fishtank.lifesize.com 2009/02/24 12:23:26.678 0:18.396 dialer:5520 OpalCon Created connection Call[i27a0b1e11]-EP[localhost/29965] 2009/02/24 12:23:26.678 0:18.396 dialer:5520 RFC2833 Handler created 2009/02/24 12:23:26.678 0:18.396 dialer:5520 RFC2833 Handler created 2009/02/24 12:23:26.678 0:18.396 dialer:5520 H460 Endpoint Attached 2009/02/24 12:23:26.678 0:18.397 dialer:5520 H323 Created new connection: localhost/29965 2009/02/24 12:23:26.678 0:18.397 dialer:5520 PCSS Outgoing call routed to h323: for Call[i27a0b1e11]-EP[1] 2009/02/24 12:23:26.678 0:18.397 dialer:5520 Call OnSetUp Call[i27a0b1e11]-EP[1] 2009/02/24 12:23:26.678 0:18.397 dialer:5520 OpalCon OnSetUpConnectionCall[i27a0b1e11]-EP[localhost/29965] 2009/02/24 12:23:26.678 0:18.397 dialer:5520 OpalEP OnSetUpConnection Call[i27a0b1e11]-EP[localhost/29965] 2009/02/24 12:23:26.678 0:18.397 dialer:5520 OpalMan SetUpCall succeeded, call=Call[i27a0b1e11] 2009/02/24 12:23:26.678 0:18.397 H225 Caller:4796 H225 Started call thread 2009/02/24 12:23:26.678 0:18.397 H225 Caller:4796 OpalCon SetPhase from UninitialisedPhase to SetUpPhase for Call[i27a0b1e11]-EP[localhost/29965] 2009/02/24 12:23:26.694 0:18.401 H225 Caller:4796 OpalCon SetPhase from SetUpPhase to SetUpPhase for Call[i27a0b1e11]-EP[localhost/29965] 2009/02/24 12:23:26.694 0:18.401 H225 Caller:4796 OpalTCP Connecting to 209.163.159.60:1720 (local port=30000) 2009/02/24 12:23:26.725 0:18.430 GMVideoOut...nager:5480 DirectX Entering processEvents 2009/02/24 12:23:26.725 0:18.431 GMVideoOut...nager:5480 DirectX Getting the window coordinates 2009/02/24 12:23:26.725 0:18.431 GMVideoOut...nager:5480 DirectX new Embedded Coordinates: 537,207 - 1177,687 2009/02/24 12:23:26.725 0:18.431 GMVideoOut...nager:5480 DirectX Leaving processEvents 2009/02/24 12:23:26.725 0:18.431 GMVideoOut...nager:5480 DirectX Entering putFrame 2009/02/24 12:23:26.725 0:18.431 GMVideoOut...nager:5480 DirectX Leaving putFrame 2009/02/24 12:23:26.725 0:18.431 GMVideoOut...nager:5480 DirectX Entering Sync 2009/02/24 12:23:26.725 0:18.434 GMVideoOut...nager:5480 DirectX Leaving Sync 2009/02/24 12:23:26.788 0:18.495 GMVideoOut...nager:5480 DirectX Entering processEvents 2009/02/24 12:23:26.788 0:18.495 GMVideoOut...nager:5480 DirectX Getting the window coordinates 2009/02/24 12:23:26.788 0:18.495 GMVideoOut...nager:5480 DirectX new Embedded Coordinates: 537,207 - 1177,687 2009/02/24 12:23:26.788 0:18.495 GMVideoOut...nager:5480 DirectX Leaving processEvents 2009/02/24 12:23:26.788 0:18.495 GMVideoOut...nager:5480 DirectX Entering putFrame 2009/02/24 12:23:26.788 0:18.495 GMVideoOut...nager:5480 DirectX Leaving putFrame 2009/02/24 12:23:26.788 0:18.496 GMVideoOut...nager:5480 DirectX Entering Sync 2009/02/24 12:23:26.788 0:18.498 GMVideoOut...nager:5480 DirectX Leaving Sync 2009/02/24 12:23:26.850 0:18.559 GMVideoOut...nager:5480 DirectX Entering processEvents 2009/02/24 12:23:26.850 0:18.559 GMVideoOut...nager:5480 DirectX Getting the window coordinates 2009/02/24 12:23:26.850 0:18.559 GMVideoOut...nager:5480 DirectX new Embedded Coordinates: 537,207 - 1177,687 2009/02/24 12:23:26.850 0:18.559 GMVideoOut...nager:5480 DirectX Leaving processEvents 2009/02/24 12:23:26.850 0:18.559 GMVideoOut...nager:5480 DirectX Entering putFrame 2009/02/24 12:23:26.850 0:18.559 GMVideoOut...nager:5480 DirectX Leaving putFrame 2009/02/24 12:23:26.850 0:18.559 GMVideoOut...nager:5480 DirectX Entering Sync 2009/02/24 12:23:26.850 0:18.562 GMVideoOut...nager:5480 DirectX Leaving Sync 2009/02/24 12:23:26.897 0:18.601 H225 Caller:4796 OpalTCP Started connection to 209.163.159.60:1720 (if=172.18.44.60:30000) 2009/02/24 12:23:26.897 0:18.601 H225 Caller:4796 H225 Sending Setup PDU 2009/02/24 12:23:26.897 0:18.607 H225 Caller:4796 Call GetMediaFormats for Call[i27a0b1e11]-EP[localhost/29965] H.264 theora H.261 H.261-CIF H.261-QCIF H.263P MPEG4 SpeexIETFWide-20.6k SpeexWB SpeexWide-20.6k iLBC G.711-uLaw-64k G.711-ALaw-64k GSM-06.10 SpeexIETFNarrow-8k SpeexNB SpeexWNarrow-8k G.726-16k G.726-24k G.726-32k G.726-40k MS-GSM 2009/02/24 12:23:26.897 0:18.607 H225 Caller:4796 H323 Could not find capability: "SpeexIETFWide-20.6k" 2009/02/24 12:23:26.897 0:18.608 H225 Caller:4796 H323 Added capability: SpeexIETFWide-20.6k <1> 2009/02/24 12:23:26.897 0:18.608 H225 Caller:4796 H323 Could not find capability: "SpeexWB" 2009/02/24 12:23:26.897 0:18.608 H225 Caller:4796 H323 Could not find capability: "SpeexWide-20.6k" 2009/02/24 12:23:26.897 0:18.608 H225 Caller:4796 H323 Added capability: SpeexWide-20.6k <2> 2009/02/24 12:23:26.897 0:18.608 H225 Caller:4796 H323 Could not find capability: "iLBC" 2009/02/24 12:23:26.897 0:18.608 H225 Caller:4796 H323 Added capability: iLBC <3> 2009/02/24 12:23:26.897 0:18.608 H225 Caller:4796 H323 Could not find capability: "G.711-uLaw-64k" 2009/02/24 12:23:26.897 0:18.608 H225 Caller:4796 H323 Added capability: G.711-uLaw-64k <4> 2009/02/24 12:23:26.897 0:18.608 H225 Caller:4796 H323 Could not find capability: "G.711-ALaw-64k" 2009/02/24 12:23:26.897 0:18.608 H225 Caller:4796 H323 Added capability: G.711-ALaw-64k <5> 2009/02/24 12:23:26.897 0:18.608 H225 Caller:4796 H323 Could not find capability: "GSM-06.10" 2009/02/24 12:23:26.897 0:18.608 H225 Caller:4796 H323 Added capability: GSM-06.10 <6> 2009/02/24 12:23:26.897 0:18.608 H225 Caller:4796 H323 Could not find capability: "SpeexIETFNarrow-8k" 2009/02/24 12:23:26.897 0:18.608 H225 Caller:4796 H323 Added capability: SpeexIETFNarrow-8k <7> 2009/02/24 12:23:26.897 0:18.608 H225 Caller:4796 H323 Could not find capability: "SpeexNB" 2009/02/24 12:23:26.897 0:18.608 H225 Caller:4796 H323 Could not find capability: "SpeexWNarrow-8k" 2009/02/24 12:23:26.897 0:18.608 H225 Caller:4796 H323 Added capability: SpeexWNarrow-8k <8> 2009/02/24 12:23:26.897 0:18.608 H225 Caller:4796 H323 Could not find capability: "G.726-16k" 2009/02/24 12:23:26.897 0:18.609 H225 Caller:4796 H323 Added capability: G.726-16k <9> 2009/02/24 12:23:26.897 0:18.609 H225 Caller:4796 H323 Could not find capability: "G.726-24k" 2009/02/24 12:23:26.897 0:18.609 H225 Caller:4796 H323 Added capability: G.726-24k <10> 2009/02/24 12:23:26.897 0:18.609 H225 Caller:4796 H323 Could not find capability: "G.726-32k" 2009/02/24 12:23:26.897 0:18.609 H225 Caller:4796 H323 Added capability: G.726-32k <11> 2009/02/24 12:23:26.897 0:18.609 H225 Caller:4796 H323 Could not find capability: "G.726-40k" 2009/02/24 12:23:26.897 0:18.609 H225 Caller:4796 H323 Added capability: G.726-40k <12> 2009/02/24 12:23:26.897 0:18.609 H225 Caller:4796 H323 Could not find capability: "MS-GSM" 2009/02/24 12:23:26.897 0:18.609 H225 Caller:4796 H323 Added capability: MS-GSM <13> 2009/02/24 12:23:26.897 0:18.609 H225 Caller:4796 H323 Could not find capability: "H.264" 2009/02/24 12:23:26.897 0:18.609 H225 Caller:4796 H323 Could not find capability: "theora" 2009/02/24 12:23:26.897 0:18.609 H225 Caller:4796 H323 Could not find capability: "H.261" 2009/02/24 12:23:26.897 0:18.609 H225 Caller:4796 H323 Added capability: H.261 <14> 2009/02/24 12:23:26.897 0:18.609 H225 Caller:4796 H323 Could not find capability: "H.261-CIF" 2009/02/24 12:23:26.897 0:18.609 H225 Caller:4796 H323 Added capability: H.261-CIF <15> 2009/02/24 12:23:26.897 0:18.609 H225 Caller:4796 H323 Could not find capability: "H.261-QCIF" 2009/02/24 12:23:26.897 0:18.609 H225 Caller:4796 H323 Added capability: H.261-QCIF <16> 2009/02/24 12:23:26.897 0:18.609 H225 Caller:4796 H323 Could not find capability: "H.263P" 2009/02/24 12:23:26.897 0:18.609 H225 Caller:4796 H323 Could not find capability: "MPEG4" 2009/02/24 12:23:26.897 0:18.610 H225 Caller:4796 H323 Added capability: UserInput/hookflash <17> 2009/02/24 12:23:26.897 0:18.610 H225 Caller:4796 H323 Added capability: UserInput/basicString <18> 2009/02/24 12:23:26.897 0:18.610 H225 Caller:4796 H323 Added capability: UserInput/dtmf <19> 2009/02/24 12:23:26.897 0:18.610 H225 Caller:4796 H323 Added capability: UserInput/RFC2833 <20> 2009/02/24 12:23:26.897 0:18.610 H225 Caller:4796 H323 Found capability: UserInput/RFC2833 <20> 2009/02/24 12:23:26.897 0:18.610 H225 Caller:4796 Call GetOtherPartyConnection Call[i27a0b1e11]-EP[localhost/29965] 2009/02/24 12:23:26.897 0:18.610 H225 Caller:4796 H323 SetLocalCapabilities: -------------- next part -------------- An HTML attachment was scrubbed... URL: From leamas.alec at gmail.com Thu Feb 26 08:39:25 2009 From: leamas.alec at gmail.com (Alec Leamas) Date: Thu, 26 Feb 2009 09:39:25 +0100 Subject: [Ekiga-list] PTLIB alsa plugin status In-Reply-To: References: <49A3BA0B.3010805@gmail.com> <49A3C7DF.1060400@gmail.com> <49A4FC57.1050104@gmail.com> <49A5CEC2.6090206@gmail.com> Message-ID: <49A6553D.9000301@gmail.com> > Yes, the ptlib alsa driver needs to be reentrant. > > > One thread could attempt to close the audio device while a second > thread is reading/writing data from/to the alsa system. Just to sort his out for my simple mind, trying to understand the overall requirements. And with the idea that using threads is perfectly reasonable in this context :-) - Let's focus on the playback case, leaving any read aside (which refer to a different alsa device). - This should mean that while one thread (A) is closing it's playback device, another thread (B) starts writing to it. - Which means that thread B has been able to open the device before thread A finished closing it(?) - Which means that I am a little confused... is this as designed? What am I missing? --a From dsandras at seconix.com Thu Feb 26 08:59:16 2009 From: dsandras at seconix.com (Damien Sandras) Date: Thu, 26 Feb 2009 09:59:16 +0100 Subject: [Ekiga-list] Incoming call failure with 3.1.1 In-Reply-To: <87ab8aosz1.fsf@ixod.org> References: <87iqn7t2io.fsf@ixod.org> <1235062650.23177.8.camel@scorpion.multitel.be> <87ab8aosz1.fsf@ixod.org> Message-ID: <1235638756.4073.14.camel@scorpion.multitel.be> Le mercredi 25 f?vrier 2009 ? 21:02 -0500, Mark T.B. Carroll a ?crit : > Damien Sandras writes: > > > Le jeudi 19 f?vrier 2009 ? 00:32 -0500, Mark T.B. Carroll a ?crit : > >> I have run through the configuration assistant thing from start to > >> finish. I can call the 500 at ekiga.net echo test and that works just fine. > >> However, calling the 520 at ekiga.net callback service has it hang up on me > >> and then ... nothing, though the -d 5 output shows that it is indeed > >> getting a callback initiated from from sip:500 at ekiga.net which is then > >> aborted. I am behind NAT and the router forwards incoming UDP from port > >> 5060 to 5100 to the machine I'm using and acts as a gateway to let all > >> my outgoing packets out. > >> > >> Should I gzip my -d 4 output and send it to somebody? I can also sniff > >> packets and send pcap files. I use Debian; software versions are, > > > > There is a known problem with incoming calls and the current snapshot. I > > will fix it this week-end. > > Now with the 20090225 one, the incoming call does arrive (yay!), I hit > `accept', and it segfaults. > > I can still send my -d 4 output to somebody. (-: A gdb backtrace would be more useful. -- _ 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 Thu Feb 26 09:30:06 2009 From: leamas.alec at gmail.com (Alec Leamas) Date: Thu, 26 Feb 2009 10:30:06 +0100 Subject: [Ekiga-list] Incoming call failure with 3.1.1 In-Reply-To: <1235638756.4073.14.camel@scorpion.multitel.be> References: <87iqn7t2io.fsf@ixod.org> <1235062650.23177.8.camel@scorpion.multitel.be> <87ab8aosz1.fsf@ixod.org> <1235638756.4073.14.camel@scorpion.multitel.be> Message-ID: <49A6611E.6040001@gmail.com> Damien Sandras wrote: > Le mercredi 25 f?vrier 2009 ? 21:02 -0500, Mark T.B. Carroll a ?crit : > >> Damien Sandras writes: >> >> >>> Le jeudi 19 f?vrier 2009 ? 00:32 -0500, Mark T.B. Carroll a ?crit : >>> >>>> I have run through the configuration assistant thing from start to >>>> finish. I can call the 500 at ekiga.net echo test and that works just fine. >>>> However, calling the 520 at ekiga.net callback service has it hang up on me >>>> and then ... nothing, though the -d 5 output shows that it is indeed >>>> getting a callback initiated from from sip:500 at ekiga.net which is then >>>> aborted. I am behind NAT and the router forwards incoming UDP from port >>>> 5060 to 5100 to the machine I'm using and acts as a gateway to let all >>>> my outgoing packets out. >>>> >>>> Should I gzip my -d 4 output and send it to somebody? I can also sniff >>>> packets and send pcap files. I use Debian; software versions are, >>>> >>> There is a known problem with incoming calls and the current snapshot. I >>> will fix it this week-end. >>> >> Now with the 20090225 one, the incoming call does arrive (yay!), I hit >> `accept', and it segfaults. >> >> I can still send my -d 4 output to somebody. (-: >> > > A gdb backtrace would be more useful. > waiting for some kind of customer "service", taking a backtrace (yes, same problem, trunk as of yesterday). --a [Thread 0x7fffe5953950 (LWP 4883) exited] [Thread 0x7fffe4f52950 (LWP 4882) exited] Program received signal SIGSEGV, Segmentation fault. 0x00000000004a0ff9 in incoming_call_response_cb ( incoming_call_popup=0x7fffeca23520, response=0, data=0x7fffffffde80) at gui/main.cpp:1418 1418 call->hangup (); Missing separate debuginfos [cut] (gdb) thread apply all bt Thread 19 (Thread 0x7fffe3b7c950 (LWP 4869)): #0 0x00000037b200b309 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007ffff6ea0222 in PSyncPoint::Wait (this=0x7fffe804abc8) at ptlib/unix/tlibthrd.cxx:1468 #2 0x00007ffff7ade927 in SIPEndPoint::SIP_PDU_Thread::Main ( this=0x7fffe804aa70) at /home/mk/src/rpms/build/opal-3.7.0/src/sip/sipep.cxx:1507 #3 0x00007ffff6e9f570 in PThread::PX_ThreadStart (arg=0x7fffe804aa70) at ptlib/unix/tlibthrd.cxx:853 #4 0x00000037b20073da in start_thread () from /lib64/libpthread.so.0 #5 0x00000037b14e62bd in clone () from /lib64/libc.so.6 Thread 12 (Thread 0x7fffedaa5950 (LWP 4857)): #0 0x00000037b14dc886 in poll () from /lib64/libc.so.6 #1 0x00000037b2c3ae08 in ?? () from /lib64/libglib-2.0.so.0 #2 0x00000037b2c3b49d in g_main_loop_run () from /lib64/libglib-2.0.so.0 #3 0x00000037bc248170 in ?? () from /usr/lib64/libORBit-2.so.0 #4 0x00000037b2c60d44 in ?? () from /lib64/libglib-2.0.so.0 #5 0x00000037b20073da in start_thread () from /lib64/libpthread.so.0 #6 0x00000037b14e62bd in clone () from /lib64/libc.so.6 Thread 11 (Thread 0x7fffee4a6950 (LWP 4850)): #0 0x00000037b14dc886 in poll () from /lib64/libc.so.6 #1 0x00000037b2c3ae08 in ?? () from /lib64/libglib-2.0.so.0 #2 0x00000037b2c3b49d in g_main_loop_run () from /lib64/libglib-2.0.so.0 #3 0x0000003b97c18d8d in ?? () from /usr/lib64/libebook-1.2.so.9 #4 0x00000037b2c60d44 in ?? () from /lib64/libglib-2.0.so.0 #5 0x00000037b20073da in start_thread () from /lib64/libpthread.so.0 #6 0x00000037b14e62bd in clone () from /lib64/libc.so.6 Thread 9 (Thread 0x7fffee745950 (LWP 4848)): #0 0x00000037b14deaa2 in select () from /lib64/libc.so.6 #1 0x00007ffff6e9f2c6 in PThread::PXBlockOnIO (this=0x9a01e0, handle=40, type=2, timeout=@0x7fffee744c20) at ptlib/unix/tlibthrd.cxx:952 #2 0x00007ffff6e94c82 in PChannel::PXSetIOBlock (this=0x99fd58, type=PChannel::PXAcceptBlock, timeout=@0x7fffee744c20) at ptlib/unix/channel.cxx:119 #3 0x00007ffff6e91340 in PSocket::os_accept (this=0x9a3200, listener=@0x99fd58, addr=0x7fffee744c70, size=0x7fffee744cfc) at ptlib/unix/socket.cxx:206 #4 0x00007ffff6ebd720 in PTCPSocket::Accept (this=0x9a3200, socket=@0x99fd58) at ptlib/common/sockets.cxx:2359 #5 0x00007ffff779dc6a in OpalListenerTCP::Accept (this=0x99fd00, timeout=@0x7fffee744e90) at /home/mk/src/rpms/build/opal-3.7.0/src/opal/transports.cxx:638 #6 0x00007ffff779df44 in OpalListener::ListenForConnections (this=0x99fd00, thread=@0x9a01e0) at /home/mk/src/rpms/build/opal-3.7.0/src/opal/transports.cxx:472 #7 0x00007ffff779e76b in OpalListener::ListenForConnections_PNotifier::Call ( this=0x9a00e0, note=@0x9a01e0, extra=0) at /home/mk/src/rpms/build/opal-3.7.0/include/opal/transports.h:355 #8 0x00007ffff6ecfe84 in PSimpleThread::Main (this=0x9a01e0) at ptlib/common/osutils.cxx:2031 #9 0x00007ffff6e9f570 in PThread::PX_ThreadStart (arg=0x9a01e0) at ptlib/unix/tlibthrd.cxx:853 #10 0x00000037b20073da in start_thread () from /lib64/libpthread.so.0 #11 0x00000037b14e62bd in clone () from /lib64/libc.so.6 Thread 8 (Thread 0x7fffee786950 (LWP 4847)): #0 0x00000037b14deaa2 in select () from /lib64/libc.so.6 #1 0x00007ffff6e90f2b in PSocket::Select (read=@0x7fffee785c70, write=@0x7fffee785b10, except=@0x7fffee785af0, timeout=@0x7fffee785e90) at ptlib/unix/socket.cxx:328 #2 0x00007ffff6ebec94 in PSocket::Select (read=@0x7fffee785c70, timeout=@0x7fffee785e90) at ptlib/common/sockets.cxx:1045 #3 0x00007ffff6ec5b82 in PMonitoredSockets::ReadFromSocket (this=0x98b830, readers=@0x7fffee785c70, socket=@0x7fffee785c68, buf=0x7fffd6fb0d20, len=65536, addr=@0x7fffee785da0, port=@0x7fffee785dce, lastReadCount=@0x7fffee785dc8, timeout=@0x7fffee785e90) at ptclib/psockbun.cxx:588 #4 0x00007ffff6ec635e in PMonitoredSocketBundle::ReadFromBundle ( this=0x98b830, buf=0x7fffd6fb0d20, len=65536, addr=@0x7fffee785da0, port=@0x7fffee785dce, iface=@0x7fffee785d40, lastReadCount=@0x7fffee785dc8, timeout=@0x7fffee785e90) at ptclib/psockbun.cxx:991 #5 0x00007ffff779a17a in OpalListenerUDP::Accept (this=0x98b730, timeout=@0x7fffee785e90) at /home/mk/src/rpms/build/opal-3.7.0/src/opal/transports.cxx:747 #6 0x00007ffff779df44 in OpalListener::ListenForConnections (this=0x98b730, thread=@0x98ca10) at /home/mk/src/rpms/build/opal-3.7.0/src/opal/transports.cxx:472 #7 0x00007ffff779e76b in OpalListener::ListenForConnections_PNotifier::Call ( this=0x98c090, note=@0x98ca10, extra=0) at /home/mk/src/rpms/build/opal-3.7.0/include/opal/transports.h:355 #8 0x00007ffff6ecfe84 in PSimpleThread::Main (this=0x98ca10) at ptlib/common/osutils.cxx:2031 #9 0x00007ffff6e9f570 in PThread::PX_ThreadStart (arg=0x98ca10) at ptlib/unix/tlibthrd.cxx:853 #10 0x00000037b20073da in start_thread () from /lib64/libpthread.so.0 #11 0x00000037b14e62bd in clone () from /lib64/libc.so.6 Thread 7 (Thread 0x7fffee7c7950 (LWP 4846)): #0 0x00000037b200b58d in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007ffff6ea0107 in PSyncPoint::Wait (this=0x83a618, waitTime=@0x7fffee7c6ef0) at ptlib/unix/tlibthrd.cxx:1486 #2 0x00007ffff6ea06a6 in PHouseKeepingThread::Main (this=0x989be0) at ptlib/unix/tlibthrd.cxx:129 #3 0x00007ffff6e9f570 in PThread::PX_ThreadStart (arg=0x989be0) at ptlib/unix/tlibthrd.cxx:853 #4 0x00000037b20073da in start_thread () from /lib64/libpthread.so.0 #5 0x00000037b14e62bd in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7fffee808950 (LWP 4845)): #0 0x00000037b200b58d in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007ffff6ea0107 in PSyncPoint::Wait (this=0x83b808, waitTime=@0x83b7b8) at ptlib/unix/tlibthrd.cxx:1486 #2 0x00007ffff6e8fc8b in PIPSocket::WaitForRouteTableChange ( timeout=@0x83b7b8, cancellation=0x83b808) at ptlib/unix/socket.cxx:1527 #3 0x00007ffff6ec7ec5 in PInterfaceMonitor::UpdateThreadMain (this=0x83b710) at ptclib/psockbun.cxx:258 #4 0x00007ffff6ecb111 in PThreadObj::Main (this=0x989930) at /home/mk/src/rpms/build/ptlib-2.7.0/include/ptlib/thread.h:599 #5 0x00007ffff6e9f570 in PThread::PX_ThreadStart (arg=0x989930) at ptlib/unix/tlibthrd.cxx:853 #6 0x00000037b20073da in start_thread () from /lib64/libpthread.so.0 #7 0x00000037b14e62bd in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7fffee849950 (LWP 4844)): #0 0x00000037b200b58d in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007ffff6ea0107 in PSyncPoint::Wait (this=0x941418, waitTime=@0x7fffee848ec0) at ptlib/unix/tlibthrd.cxx:1486 #2 0x00007ffff7750514 in OpalManager::GarbageMain (this=0x940a60) at /home/mk/src/rpms/build/opal-3.7.0/src/opal/manager.cxx:1542 #3 0x00007ffff775707b in OpalManager::GarbageMain_PNotifier::Call ( this=0x982890, note=@0x93fc00, extra=0) at /home/mk/src/rpms/build/opal-3.7.0/include/opal/manager.h:1369 #4 0x00007ffff6ecfe84 in PSimpleThread::Main (this=0x93fc00) at ptlib/common/osutils.cxx:2031 #5 0x00007ffff6e9f570 in PThread::PX_ThreadStart (arg=0x93fc00) at ptlib/unix/tlibthrd.cxx:853 #6 0x00000037b20073da in start_thread () from /lib64/libpthread.so.0 #7 0x00000037b14e62bd in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7fffee88a950 (LWP 4843)): #0 0x00000037b200b309 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007ffff6ea0222 in PSyncPoint::Wait (this=0x8ed938) at ptlib/unix/tlibthrd.cxx:1468 #2 0x00000000005a2a4f in GMVideoOutputManager::Main (this=0x8ed6f0) at ../../../../lib/engine/components/common-videooutput/videooutput-manager-common.cpp:92 #3 0x00007ffff6e9f570 in PThread::PX_ThreadStart (arg=0x8ed6f0) at ptlib/unix/tlibthrd.cxx:853 #4 0x00000037b20073da in start_thread () from /lib64/libpthread.so.0 #5 0x00000037b14e62bd in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7fffee8cb950 (LWP 4842)): #0 0x00000037b200b58d in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007ffff6ea0107 in PSyncPoint::Wait (this=0x8eacc0, waitTime=@0x7fffee8caec0) at ptlib/unix/tlibthrd.cxx:1486 #2 0x000000000058b8ee in Ekiga::AudioEventScheduler::Main (this=0x8eabe8) at ../../../lib/engine/audiooutput/audiooutput-scheduler.cpp:83 #3 0x00007ffff6e9f570 in PThread::PX_ThreadStart (arg=0x8eabe8) at ptlib/unix/tlibthrd.cxx:853 #4 0x00000037b20073da in start_thread () from /lib64/libpthread.so.0 #5 0x00000037b14e62bd in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fffee90c950 (LWP 4841)): #0 0x00000037b200b309 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007ffff6ea0222 in PSyncPoint::Wait (this=0x8ea6e8) at ptlib/unix/tlibthrd.cxx:1468 #2 0x000000000050d1a5 in Ekiga::VideoInputCore::VideoPreviewManager::Main ( this=0x8ea528) at ../../../lib/engine/videoinput/videoinput-core.cpp:106 #3 0x00007ffff6e9f570 in PThread::PX_ThreadStart (arg=0x8ea528) at ptlib/unix/tlibthrd.cxx:853 #4 0x00000037b20073da in start_thread () from /lib64/libpthread.so.0 #5 0x00000037b14e62bd in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7ffff6b247b0 (LWP 4832)): #0 0x00000000004a0ff9 in incoming_call_response_cb ( incoming_call_popup=0x7fffeca23520, response=0, data=0x7fffffffde80) at gui/main.cpp:1418 #1 0x00000037b340b7dd in g_closure_invoke () from /lib64/libgobject-2.0.so.0 #2 0x00000037b34214bd in ?? () from /lib64/libgobject-2.0.so.0 #3 0x00000037b3422b68 in g_signal_emit_valist () from /lib64/libgobject-2.0.so.0 #4 0x00000037b3423093 in g_signal_emit () from /lib64/libgobject-2.0.so.0 #5 0x00000037b340b7dd in g_closure_invoke () from /lib64/libgobject-2.0.so.0 #6 0x00000037b34214bd in ?? () from /lib64/libgobject-2.0.so.0 #7 0x00000037b3422b68 in g_signal_emit_valist () from /lib64/libgobject-2.0.so.0 #8 0x00000037b3423093 in g_signal_emit () from /lib64/libgobject-2.0.so.0 #9 0x00000037b98850fd in ?? () from /usr/lib64/libgtk-x11-2.0.so.0 #10 0x00000037b340b7dd in g_closure_invoke () from /lib64/libgobject-2.0.so.0 #11 0x00000037b3420dd8 in ?? () from /lib64/libgobject-2.0.so.0 #12 0x00000037b3422b68 in g_signal_emit_valist () from /lib64/libgobject-2.0.so.0 #13 0x00000037b3423093 in g_signal_emit () from /lib64/libgobject-2.0.so.0 #14 0x00000037b988434d in ?? () from /usr/lib64/libgtk-x11-2.0.so.0 #15 0x00000037b9929a08 in ?? () from /usr/lib64/libgtk-x11-2.0.so.0 #16 0x00000037b340b7dd in g_closure_invoke () from /lib64/libgobject-2.0.so.0 #17 0x00000037b342119b in ?? () from /lib64/libgobject-2.0.so.0 #18 0x00000037b34229ea in g_signal_emit_valist () from /lib64/libgobject-2.0.so.0 #19 0x00000037b3423093 in g_signal_emit () from /lib64/libgobject-2.0.so.0 #20 0x00000037b9a2c7de in ?? () from /usr/lib64/libgtk-x11-2.0.so.0 #21 0x00000037b9922373 in gtk_propagate_event () from /usr/lib64/libgtk-x11-2.0.so.0 #22 0x00000037b9923493 in gtk_main_do_event () from /usr/lib64/libgtk-x11-2.0.so.0 #23 0x00000037bae4deac in ?? () from /usr/lib64/libgdk-x11-2.0.so.0 #24 0x00000037b2c3779b in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #25 0x00000037b2c3af6d in ?? () from /lib64/libglib-2.0.so.0 #26 0x00000037b2c3b49d in g_main_loop_run () from /lib64/libglib-2.0.so.0 #27 0x00000037b99238a7 in gtk_main () from /usr/lib64/libgtk-x11-2.0.so.0 #28 0x00000000004aa0ec in main (argc=1, argv=0x7fffffffe448) at gui/main.cpp:4562 (gdb) k Kill the program being debugged? (y or n) (gdb) q From opeyer at nimr.mrc.ac.uk Thu Feb 26 09:41:04 2009 From: opeyer at nimr.mrc.ac.uk (opeyer at nimr.mrc.ac.uk) Date: Thu, 26 Feb 2009 09:41:04 +0000 Subject: [Ekiga-list] ekiga beginner questions In-Reply-To: References: <1235580916.5512.31.camel@scorpion.multitel.be><1235587463.3978.3.camel@scorpion.multitel.be> Message-ID: <894996400-1235642552-cardhu_decombobulator_blackberry.rim.net-1048038447-@bxe1036.bisx.produk.on.blackberry> For MacOS, try Xmeeting. I have done some Xmeeting<>Ekiga calls. O ------------------ 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 -----Original Message----- From: "H. S." Date: Wed, 25 Feb 2009 13:48:51 To: Ekiga mailing list Subject: Re: [Ekiga-list] ekiga beginner questions _______________________________________________ ekiga-list mailing list ekiga-list at gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list From res3stockm at catalysis.at Thu Feb 26 10:28:27 2009 From: res3stockm at catalysis.at (Michael Stockenhuber) Date: Thu, 26 Feb 2009 21:28:27 +1100 (EST) Subject: [Ekiga-list] call failure Message-ID: <1497515573.61235644107546.JavaMail.open-xchange@sam> Hi all, ?I am using ekiga from current debian experimental (3.0.1) to connect to ekiga? on a windows vista machine (cough,cough). It connects often from boith sides, but afetr 30 s or so connection goes to zero transfer rate. When I phone 500 it works reasonably well, but with 520 the callback dies more or less immediately. Any suggestions? Cheers Michael -------------- next part -------------- An HTML attachment was scrubbed... URL: From palos at post.sk Thu Feb 26 11:17:22 2009 From: palos at post.sk (Palo S.) Date: 26 Feb 2009 12:17:22 +0100 (CET) Subject: [Ekiga-list] ekiga on Slackware 12.2 not workingusefully... any suggestions? Message-ID: <49A67A42.000001.20909@kamasutra> > > Now ekiga sees my camera. However > (1) if it receives a call from an ekiga 3.0.1 or 3.1.0 system it seg > faults and dies. > It also makes the complaints > > ** (ekiga:22591): CRITICAL **: gm_conf_get_string: assertion `key /apps/ekiga/general/user_interface/main_window/size has no corresponding entry! \' failed > > ** (ekiga:22591): CRITICAL **: entry_get_bool: assertion `gmconf key /apps/ekiga/general/nat/disable_stun is of type GM_CONF_BOOL\' failed > This really looks like gconf/gnome related issue. However I cannot say whether this cause the problem. > > I have to assume that there is some weird thing going on in my system > that none/few of you see. Is there anyone here (besides me) else > using it with > --disable-gnome --disable-gconf > > Thanks for any suggestions anyone can provide. Maybe you can try to compile with gnome and gconf support? In order to find out whether it is the cause of the problem or something else is on blame... P. __________ http://www.pnp.sk - pridajte svoje fotky na PaciNepaci From Jim.Diamond at acadiau.ca Thu Feb 26 12:40:05 2009 From: Jim.Diamond at acadiau.ca (Jim Diamond) Date: Thu, 26 Feb 2009 08:40:05 -0400 Subject: [Ekiga-list] ekiga on Slackware 12.2 not working usefully... any suggestions? In-Reply-To: <49A67A42.000001.20909@kamasutra> References: <49A67A42.000001.20909@kamasutra> Message-ID: <20090226124005.GA9793@jdiamond-nb> On Thu, Feb 26, 2009 at 12:17 (+0100), Palo S. wrote: >> Now ekiga sees my camera. However >> (1) if it receives a call from an ekiga 3.0.1 or 3.1.0 system it seg >> faults and dies. >> It also makes the complaints >> ** (ekiga:22591): CRITICAL **: gm_conf_get_string: assertion `key /apps/ekiga/general/user_interface/main_window/size has no corresponding entry! \' failed >> ** (ekiga:22591): CRITICAL **: entry_get_bool: assertion `gmconf key /apps/ekiga/general/nat/disable_stun is of type GM_CONF_BOOL\' failed > This really looks like gconf/gnome related issue. > However I cannot say whether this cause the problem. >> I have to assume that there is some weird thing going on in my system >> that none/few of you see. Is there anyone here (besides me) else >> using it with >> --disable-gnome --disable-gconf >> Thanks for any suggestions anyone can provide. > Maybe you can try to compile with gnome and gconf > support? In order to find out whether it is the > cause of the problem or something else is on > blame... Unfortunately, Slackware 12.2 does not come with gnome/gconf. There are some 3rd-party gnome packages, but they all seem to come with 4th-party stories telling of how some critical libraries get over-written, causing "mysterious" problems with other programs. Consequently, I am loathe to do so. Thanks for the suggestion, though. Certainly, I expect the error messages above to be related to imperfect implementation of --disable-gnome --disable-gconf but I'm having a harder time imagining that the reason for the bizarre video problem is a gnomish thing. However, I say that with never having taken a peek at any of the ekiga/ptlib/opal code. Thanks. Jim From Eugen.Dedu at pu-pm.univ-fcomte.fr Thu Feb 26 14:49:48 2009 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Thu, 26 Feb 2009 15:49:48 +0100 Subject: [Ekiga-list] ekiga-snapshot-config-tool Debian packaging looks for wrong schema file In-Reply-To: <87ocwyqw5o.fsf@ixod.org> References: <87ocwyqw5o.fsf@ixod.org> Message-ID: <49A6AC0C.10402@pu-pm.univ-fcomte.fr> Mark T.B. Carroll wrote: > ekiga-snapshot-config-tool --install-schemas gives, > > I/O warning : failed to load external entity "/etc/gconf/schemas/ekiga.schemas" > Failed to open `/etc/gconf/schemas/ekiga.schemas': No such file or directory > > My version of the ekiga-snapshot Debian package is 0-20090214-1 which > instead has a /usr/share/gconf/schemas/ekiga-snapshot.schemas file. upstream, please apply the patch attached. Do you think it is still useful to distribute this small script? Is it better to just inform people about the gconftool command line to remove their ekiga configuration? -- Eugen -------------- next part -------------- A non-text attachment was scrubbed... Name: ct.patch Type: text/x-patch Size: 1092 bytes Desc: not available URL: From Eugen.Dedu at pu-pm.univ-fcomte.fr Thu Feb 26 15:30:32 2009 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Thu, 26 Feb 2009 16:30:32 +0100 Subject: [Ekiga-list] call failure In-Reply-To: <1497515573.61235644107546.JavaMail.open-xchange@sam> References: <1497515573.61235644107546.JavaMail.open-xchange@sam> Message-ID: <49A6B598.3020305@pu-pm.univ-fcomte.fr> Michael Stockenhuber wrote: > Hi all, > > I am using ekiga from current debian experimental (3.0.1) to connect to ekiga > on a windows vista machine (cough,cough). It connects often from boith sides, > but afetr 30 s or so connection goes to zero transfer rate. When I phone 500 it > works reasonably well, but with 520 the callback dies more or less immediately. I had the same problem with linux->windows. Could you give us a -d 4 output? (See wiki, debugging). For crash: could you provide a gdb stack bt? -- Eugen From derek at indranet.co.nz Thu Feb 26 21:24:48 2009 From: derek at indranet.co.nz (Derek Smithies) Date: Fri, 27 Feb 2009 10:24:48 +1300 (NZDT) Subject: [Ekiga-list] PTLIB alsa plugin status In-Reply-To: <49A6553D.9000301@gmail.com> References: <49A3BA0B.3010805@gmail.com> <49A3C7DF.1060400@gmail.com> <49A4FC57.1050104@gmail.com> <49A5CEC2.6090206@gmail.com> <49A6553D.9000301@gmail.com> Message-ID: Hi, On Thu, 26 Feb 2009, Alec Leamas wrote: > Just to sort his out, trying to understand the overall requirements. Which is a very reasonable thing to do, and it is a good question. >And with the idea that using threads is perfectly reasonable in this context :-) Excellent. This idea is very reasonable. > > -Let's focus on the playback case, leaving any read aside (which refer to a > different alsa device). Good idea. > > - This should mean that while one thread (A) is closing it's playback > device, another thread (B) starts writing to it. Yes, thread B is writing audio to the playback device. Thread B is collecting the data off the jitter buffer, decoding the audio using the specified codec, sending the data to the playback device. thread B is stopped by a bad write to the playback device. Typically, a bad write to the playback device is caused by the playback device being closed. In the gui thread, user clicked hangup, and a close down thread is created. This close down thread runs independantly of the gui (so does not hold up the gui so responses work ok) and makes a call to OpalCall::Clear() (which is a structure inside Opal) which then goes through all the RTP threads (including audio) and closes the devices. Since the Open, Close and Read/Write operations are atomic, there is no possibility of one happening while the other happens and breaking things. The Opal thread which does the call to device Open then goes on to launch the read/write threads. So read/writes don't run before the device is open. I don't think this aspect of the the Opal design is a problem. The problem we are are trying to address is the reason for the buffering - why is there a 100ms delay??? Answer: There are two entities that I have seen which can "store" audio to give you a delay. The jitter buffer, which can store seconds of audio. There are status variables in the jitter buffer which indicate how long it is buffering audio for. The sound device. Opal sets the sound device (on linux) to store 2 buffers of audio, which is (at most) 2 x 30ms. One of the 30ms buffers is the buffer currently being written to the sound device. The second 30ms buffer is the next buffer to be written. The buffering depth is set by the call to devices/audiodev.cpp:bool PSoundChannel_EKIGA::SetBuffers (PINDEX size, PINDEX count) size is <=480 (480 is for a 30ms long buffer. GSM uses 20ms.) count is typically 2 (windows uses 3 or more) It "is" possible that this call is not happening at the right time. I doubt this, but you could verify this with a review of the logs. If this command was being missed, the sound device would get whatever value it is defaulted to.. Derek. -- Derek Smithies Ph.D. IndraNet Technologies Ltd. Email: derek at indranet.co.nz ph +64 3 365 6485 Web: http://www.indranet-technologies.com/ From leamas.alec at gmail.com Thu Feb 26 23:30:21 2009 From: leamas.alec at gmail.com (Alec Leamas) Date: Fri, 27 Feb 2009 00:30:21 +0100 Subject: [Ekiga-list] PTLIB alsa plugin status In-Reply-To: References: <49A3BA0B.3010805@gmail.com> <49A3C7DF.1060400@gmail.com> <49A4FC57.1050104@gmail.com> <49A5CEC2.6090206@gmail.com> <49A6553D.9000301@gmail.com> Message-ID: <49A7260D.8020705@gmail.com> Derek Smithies wrote: > Hi, > On Thu, 26 Feb 2009, Alec Leamas wrote: > >> Just to sort his out, trying to understand the overall requirements. > Which is a very reasonable thing to do, and it is a good question. > >> And with the idea that using threads is perfectly reasonable in this >> context :-) > Excellent. This idea is very reasonable. >> >> -Let's focus on the playback case, leaving any read aside (which >> refer to a different alsa device). > Good idea. > >> >> - This should mean that while one thread (A) is closing it's >> playback device, another thread (B) starts writing to it. > Yes, thread B is writing audio to the playback device. Thread B is > collecting the data off the jitter buffer, > decoding the audio using the specified codec, > sending the data to the playback device. > > thread B is stopped by a bad write to the playback device. Typically, > a bad write to the playback device is caused by the playback device > being closed. Hm... a write operation could be guaranteed to return in finite time (using non-blocking io + snd_pcm_wait). So couldn't the close method just mark the chanell as closing, leaving the dirty work to the "writer" thread and thus avoiding the locks? (Which, otoh, really isn't a big issue in this scenario). If required, opening could be handled in the same way, I guess. This would also create the advantage that the thread could process the jitter buffer data in parallel with the alsa output, without the need to wait for the IO to complete. Wouldn't this give a more accurate timing? Also, avoiding blocking io is a Good Thing IMHO. Something like while(1) { if( closing) close(); return chunk = process_jitter_buffer(); snd_pcm_wait( pcm, timeout) if( timeout) // close or prepare... else snd_pcm_write( pcm , chunk) // non blocking } > > In the gui thread, user clicked hangup, and a close down thread is > created. This close down thread runs independantly of the gui (so does > not hold up the gui so responses work ok) and makes a call to > OpalCall::Clear() (which is a structure inside Opal) which then goes > through all the RTP threads (including audio) and closes the devices. > > Since the Open, Close and Read/Write operations are atomic, there is > no possibility of one happening while the other happens and breaking > things. > > The Opal thread which does the call to device Open then goes on to > launch the read/write threads. So read/writes don't run before the > device is open. Thanks. So there are never any io operations in parallell, but parallell io/close operations. I think I understand. A good explanation, BTW. I might submit a patch with documentation to the plugin base class clarifying this, basically what we have here. > > I don't think this aspect of the the Opal design is a problem. The > problem we are are trying to address is the reason for the buffering - > why is there a 100ms delay??? Yes. I *think* I've seen five periods hardcoded somewhere... > Answer: > There are two entities that I have seen which can "store" audio to > give you a delay. > The jitter buffer, which can store seconds of audio. > There are status variables in the jitter buffer which indicate how > long it is buffering audio for. As I suspected. Thanks also for this. So basically we have network latency, jitter/echo cancellation buffer and the device/alsa buffer, all in total preferably in the 150 - 200 ms range. If there is no echo cancellation, the alsa buffer (if larger) could also be jitter buffer. But not if fancy things like echo cancellation should be performed (?). > > The sound device. Opal sets the sound device (on linux) to store 2 > buffers of audio, which is (at most) 2 x 30ms. > One of the 30ms buffers is the buffer currently being written to the > sound device. > The second 30ms buffer is the next buffer to be written. > > The buffering depth is set by the call to > devices/audiodev.cpp:bool PSoundChannel_EKIGA::SetBuffers (PINDEX > size, PINDEX count) > > size is <=480 (480 is for a 30ms long buffer. GSM uses 20ms.) > count is typically 2 (windows uses 3 or more) > > It "is" possible that this call is not happening at the right time. I > doubt this, but you could verify this with a review of the logs. > If this command was being missed, the sound device would get whatever > value it is defaulted to.. The thing is that when looking at the alsa device from the operating system level (in the /proc filesystem) it's clear that the buffer is 5 periods * 20 ms = 100 ms (details in the thread initiated by Andrea). So something is not as expected... Is the simple truth that the alsa period size doesn't match the codec chunk size? But even if so, should it matter? "suspicious" > > Derek. --a From derek at indranet.co.nz Fri Feb 27 01:07:05 2009 From: derek at indranet.co.nz (Derek Smithies) Date: Fri, 27 Feb 2009 14:07:05 +1300 (NZDT) Subject: [Ekiga-list] PTLIB alsa plugin status In-Reply-To: <49A7260D.8020705@gmail.com> References: <49A3BA0B.3010805@gmail.com> <49A3C7DF.1060400@gmail.com> <49A4FC57.1050104@gmail.com> <49A5CEC2.6090206@gmail.com> <49A6553D.9000301@gmail.com> <49A7260D.8020705@gmail.com> Message-ID: Hi, On Fri, 27 Feb 2009, Alec Leamas wrote: > Hm... a write operation could be guaranteed to return in finite time (using > non-blocking io + snd_pcm_wait). So couldn't the close method just mark the > chanell as closing, leaving the dirty work to the "writer" thread and thus > avoiding the locks? (Which, otoh, really isn't a big issue in this scenario). > If required, opening could be handled in the same way, I guess. This would > also create the advantage that the thread could process the jitter buffer > data in parallel with the alsa output, without the need to wait for the IO to > complete. Wouldn't this give a more accurate timing? Also, avoiding blocking > io is a Good Thing IMHO. No. It must be a blocking write. The architecture of opal demands this. The play thread (using play as an example) repeatedly does the following read rtp packet from jitter buffer decode put raw audio to sound device (which delays for up to framesize of packet) There was a time when pwlib and openh323 (the old names of ptlib and opal) used non blocking writes to the sound card plus software timers. the software timers were found to not be reliable enough to delay the write thread. Sometimes the delay was hundreds of milliseconds. So openh323 and pwlib were changed to use blocking writes, which gave much better audio performance. to change the operation of the write to be non blocking would have major architectural implications to opal. Let me help you. This won't happen. >> I don't think this aspect of the the Opal design is a problem. The problem >> we are are trying to address is the reason for the buffering - why is there >> a 100ms delay??? > Yes. I *think* I've seen five periods hardcoded somewhere... Can you find the hardcoded bit? And report it? >> Answer: >> There are two entities that I have seen which can "store" audio to give you >> a delay. >> The jitter buffer, which can store seconds of audio. >> There are status variables in the jitter buffer which indicate how long it >> is buffering audio for. > As I suspected. Thanks also for this. So basically we have network latency, > jitter/echo cancellation buffer and the device/alsa buffer, all in total > preferably in the 150 - 200 ms range. If there is no echo cancellation, the > alsa buffer (if larger) could also be jitter buffer. But not if fancy things > like echo cancellation should be performed (?). You may have the answer here. How much delay does the speex echo cancellor introduce ? >> it is defaulted to.. > The thing is that when looking at the alsa device from the operating system > level (in the /proc filesystem) it's clear that the buffer is 5 periods * 20 > ms = 100 ms (details in the thread initiated by Andrea). So something is not > as expected... Is the simple truth that the alsa period size doesn't match > the codec chunk size? But even if so, should it matter? "suspicious" Alsa probably introduces a delay/buffering of its own when you do alsa<-->pulse conversions. Can you repeat the above test on an older distro where the machine does not have pulse? Derek. -- Derek Smithies Ph.D. IndraNet Technologies Ltd. Email: derek at indranet.co.nz ph +64 3 365 6485 Web: http://www.indranet-technologies.com/ From leepatricklee at gmail.com Fri Feb 27 04:12:39 2009 From: leepatricklee at gmail.com (Patrick Lee) Date: Fri, 27 Feb 2009 12:12:39 +0800 Subject: [Ekiga-list] direct IP to IP SIP call without SIP registrar, not working in 3.x Message-ID: <6653d8470902262012g6ad8a1f6i3899301733ae146c@mail.gmail.com> Not sure any one has asked this question before. I was able to make call without registering any SIP registrar in Ekiga ver 2.x. No need to create SIP account. Just type "sip:192.168.1.34" (the remote IP address) and the call was setup. And the remote client could be x-lite. But NOT with ver 3.x, the same syntax gave me no response. It seems like I have to create a SIP account first. My environment is a complete isolated network so I simply can't register in ekiga.net for SIP account. And there is some other SIP clients so I have to stick with SIP protocol. I know SIP registration is a proper SIP operation. But I love ekiga as it allows pt-to-pt call without setting up a SIP server. But not true for ver 3.x. Any solution ? Patrick From DAVE.HIGTON at nice.com Fri Feb 27 07:37:08 2009 From: DAVE.HIGTON at nice.com (Dave Higton) Date: Fri, 27 Feb 2009 07:37:08 -0000 Subject: [Ekiga-list] direct IP to IP SIP call without SIP registrar, not working in 3.x In-Reply-To: <6653d8470902262012g6ad8a1f6i3899301733ae146c@mail.gmail.com> References: <6653d8470902262012g6ad8a1f6i3899301733ae146c@mail.gmail.com> Message-ID: Patrick Lee wrote: > Not sure any one has asked this question before. > > I was able to make call without registering any SIP registrar in Ekiga > ver 2.x. No need to create SIP account. > Just type "sip:192.168.1.34" (the remote IP address) and the > call was setup. > And the remote client could be x-lite. > > But NOT with ver 3.x, the same syntax gave me no response. It seems > like I have to create a SIP account first. > > My environment is a complete isolated network so I simply can't > register in ekiga.net for SIP account. > And there is some other SIP clients so I have to stick with > SIP protocol. > > I know SIP registration is a proper SIP operation. But I love ekiga > as it allows pt-to-pt call without setting up a SIP server. But not > true for ver 3.x. Any solution ? It may be worth mentioning that I have the same situation (no SIP access to the outside world, therefore Ekiga cannot possibly register to anything), the same requirement to do VoIP across our own LAN (only), and the same problem. Dave NICE CTI Systems UK Limited ("NICE") is registered in England under company number, 3403044. The registered office of NICE is at Tollbar Way, Hedge End, Southampton, Hampshire SO30 2ZP. Confidentiality: This communication and any attachments are intended for the above-named persons only and may be confidential and/or legally privileged. Any opinions expressed in this communication are not necessarily those of NICE. If this communication has come to you in error you must take no action based on it, nor must you copy or show it to anyone; please delete/destroy and inform the sender by e-mail immediately. Monitoring: NICE may monitor incoming and outgoing e-mails. Viruses: Although we have taken steps toward ensuring that this e-mail and attachments are free from any virus, we advise that in keeping with good computing practice the recipient should ensure they are actually virus free. From garmellin at gpi.it Fri Feb 27 07:53:45 2009 From: garmellin at gpi.it (Giampaolo Armellin) Date: Fri, 27 Feb 2009 08:53:45 +0100 Subject: [Ekiga-list] [ekiga engine] api availability and documentation Message-ID: <20090227075422.C0C4E10E7@mailweb.gpi.it> I've read on Ekiga web site that the engine is available to be used in other projects. Nevertheless, I couldn't find any reference to a SDK, API or documents. May anyone tell me where that information can be found? Thanks a lot Giampaolo Armellin -------------- next part -------------- An HTML attachment was scrubbed... URL: From michel.memeteau at gmail.com Fri Feb 27 07:59:38 2009 From: michel.memeteau at gmail.com (michel memeteau) Date: Fri, 27 Feb 2009 08:59:38 +0100 Subject: [Ekiga-list] direct IP to IP SIP call without SIP registrar, not working in 3.x In-Reply-To: References: <6653d8470902262012g6ad8a1f6i3899301733ae146c@mail.gmail.com> Message-ID: Did you both tried sip:anything at IP ? On Fri, Feb 27, 2009 at 8:37 AM, Dave Higton wrote: > Patrick Lee wrote: > > > Not sure any one has asked this question before. > > > > I was able to make call without registering any SIP registrar in Ekiga > > ver 2.x. No need to create SIP account. > > Just type "sip:192.168.1.34" (the remote IP address) and the > > call was setup. > > And the remote client could be x-lite. > > > > But NOT with ver 3.x, the same syntax gave me no response. It seems > > like I have to create a SIP account first. > > > > My environment is a complete isolated network so I simply can't > > register in ekiga.net for SIP account. > > And there is some other SIP clients so I have to stick with > > SIP protocol. > > > > I know SIP registration is a proper SIP operation. But I love ekiga > > as it allows pt-to-pt call without setting up a SIP server. But not > > true for ver 3.x. Any solution ? > > It may be worth mentioning that I have the same situation (no SIP > access to the outside world, therefore Ekiga cannot possibly > register to anything), the same requirement to do VoIP across our > own LAN (only), and the same problem. > > Dave > > > NICE CTI Systems UK Limited ("NICE") is registered in England under company > number, 3403044. The registered office of NICE is at Tollbar Way, Hedge End, > Southampton, Hampshire SO30 2ZP. > > Confidentiality: This communication and any attachments are intended for > the above-named persons only and may be confidential and/or legally > privileged. Any opinions expressed in this communication are not necessarily > those of NICE. If this communication has come to you in error you must take > no action based on it, nor must you copy or show it to anyone; please > delete/destroy and inform the sender by e-mail immediately. > > Monitoring: NICE may monitor incoming and outgoing e-mails. > > Viruses: Although we have taken steps toward ensuring that this e-mail and > attachments are free from any virus, we advise that in keeping with good > computing practice the recipient should ensure they are actually virus free. > _______________________________________________ > 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 leamas.alec at gmail.com Fri Feb 27 08:37:36 2009 From: leamas.alec at gmail.com (Alec Leamas) Date: Fri, 27 Feb 2009 09:37:36 +0100 Subject: [Ekiga-list] PTLIB alsa plugin status In-Reply-To: References: <49A3BA0B.3010805@gmail.com> <49A3C7DF.1060400@gmail.com> <49A4FC57.1050104@gmail.com> <49A5CEC2.6090206@gmail.com> <49A6553D.9000301@gmail.com> <49A7260D.8020705@gmail.com> Message-ID: <49A7A650.3080805@gmail.com> Derek Smithies wrote: > Hi, > > On Fri, 27 Feb 2009, Alec Leamas wrote: > >> Hm... a write operation could be guaranteed to return in finite time >> (using non-blocking io + snd_pcm_wait). So couldn't the close method >> just mark the chanell as closing, leaving the dirty work to the >> "writer" thread and thus avoiding the locks? (Which, otoh, really >> isn't a big issue in this scenario). If required, opening could be >> handled in the same way, I guess. This would also create the >> advantage that the thread could process the jitter buffer data in >> parallel with the alsa output, without the need to wait for the IO to >> complete. Wouldn't this give a more accurate timing? Also, avoiding >> blocking io is a Good Thing IMHO. > > No. > It must be a blocking write. The architecture of opal demands this. > > The play thread (using play as an example) repeatedly does the following > read rtp packet from jitter buffer > decode > put raw audio to sound device (which delays for up to framesize of > packet) > I didn't really make my point clear, sorry. I understand that the write method should block, and my code does this, it's just a question how it's implemented. Refactored to a write method: write( pcm, chunk) if( closing) close(); return(); snd_pcm_wait( pcm, timeout) // Blocks until there is a free frame in alsa buffer, // the same time as a blocking write would, using the // the same "timer", but with a timeout option. if( timeout) // Underrun? Check status & handle error. else write( pcm, chunk) // non-blocking The basic difference is that this code will never block indefinitely - thus making it it possible to remove the locks. Depending on the blocking, alsa write implementation it might also give a slightly better timing. But I shouldn't count on it. > > There was a time when pwlib and openh323 (the old names of ptlib and > opal) > used non blocking writes to the sound card plus software timers. the > software timers were found to not be reliable enough to delay the > write thread. Sometimes the delay was hundreds of milliseconds. So > openh323 and pwlib were changed to use blocking writes, which gave > much better audio performance. > > to change the operation of the write to be non blocking would have > major architectural implications to opal. Let me help you. This won't > happen. Agreed Coming back to the other issues. Unfortunately, I'm the victim of https://bugzilla.redhat.com/show_bug.cgi?id=481722, having a hard time to to test Ekiga. I'll do what I can, though. From leepatricklee at gmail.com Fri Feb 27 08:59:53 2009 From: leepatricklee at gmail.com (Patrick Lee) Date: Fri, 27 Feb 2009 16:59:53 +0800 Subject: [Ekiga-list] direct IP to IP SIP call without SIP registrar, not working in 3.x In-Reply-To: References: <6653d8470902262012g6ad8a1f6i3899301733ae146c@mail.gmail.com> Message-ID: <6653d8470902270059q1261cad0v6a1595acd176df99@mail.gmail.com> are you suggesting "sip:hostname at dest_IP" where "hostname" can be anything and "dest_IP" is the remote endpoint IP address ? I tried "sip:abc at 192.168.1.34", it returned nothing, no connecting tone nor busying tone From chinku.linux at gmail.com Fri Feb 27 09:12:24 2009 From: chinku.linux at gmail.com (chaitanya mehandru) Date: Fri, 27 Feb 2009 14:42:24 +0530 Subject: [Ekiga-list] direct IP to IP SIP call without SIP registrar, not working in 3.x In-Reply-To: <6653d8470902270059q1261cad0v6a1595acd176df99@mail.gmail.com> References: <6653d8470902262012g6ad8a1f6i3899301733ae146c@mail.gmail.com> <6653d8470902270059q1261cad0v6a1595acd176df99@mail.gmail.com> Message-ID: <24b40b2b0902270112w28cec971j40765dd1ef3540bc@mail.gmail.com> Just for your info, I have been using ekiga 3.0.2 on Ubuntu hardy and I can connect using - sip:abc at w.x.y.z. I hear busy tone,connecting tone & ringing tone. On Fri, Feb 27, 2009 at 2:29 PM, Patrick Lee wrote: > are you suggesting "sip:hostname at dest_IP" > where "hostname" can be anything and "dest_IP" is the remote endpoint > IP address ? > > I tried "sip:abc at 192.168.1.34 ", it returned > nothing, no connecting > tone nor busying tone > _______________________________________________ > 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 res3stockm at catalysis.at Fri Feb 27 09:52:17 2009 From: res3stockm at catalysis.at (Michael Stockenhuber) Date: Fri, 27 Feb 2009 20:52:17 +1100 (EST) Subject: [Ekiga-list] call failure In-Reply-To: <49A6B598.3020305@pu-pm.univ-fcomte.fr> References: <1497515573.61235644107546.JavaMail.open-xchange@sam> <49A6B598.3020305@pu-pm.univ-fcomte.fr> Message-ID: <1262408424.101235728337933.JavaMail.open-xchange@sam> Hi, I have replied and sent the logs but they are too big and wait for moderator approval. Cheers Michael On February 27, 2009 at 2:30 AM Eugen Dedu wrote: > Michael Stockenhuber wrote: > > Hi all, > > > >? I am using ekiga from current debian experimental (3.0.1) to connect to > >ekiga > > on a windows vista machine (cough,cough). It connects often from boith > > sides, > > but afetr 30 s or so connection goes to zero transfer rate. When I phone 500 > > it > > works reasonably well, but with 520 the callback dies more or less > > immediately. > > I had the same problem with linux->windows.? Could you give us a -d 4 > output?? (See wiki, debugging). > > For crash: could you provide a gdb stack bt? > > -- > Eugen > _______________________________________________ > 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 leepatricklee at gmail.com Fri Feb 27 11:18:31 2009 From: leepatricklee at gmail.com (Patrick Lee) Date: Fri, 27 Feb 2009 19:18:31 +0800 Subject: [Ekiga-list] direct IP to IP SIP call without SIP registrar, not working in 3.x In-Reply-To: <24b40b2b0902270112w28cec971j40765dd1ef3540bc@mail.gmail.com> References: <6653d8470902262012g6ad8a1f6i3899301733ae146c@mail.gmail.com> <6653d8470902270059q1261cad0v6a1595acd176df99@mail.gmail.com> <24b40b2b0902270112w28cec971j40765dd1ef3540bc@mail.gmail.com> Message-ID: <6653d8470902270318xf2b75eq128dc1c73f5e1706@mail.gmail.com> I am on Windows platform, and I found similar problem in h.323 as well. Look like something wrong with the windows executable. But ver 2.x works fine on my windows box. On Fri, Feb 27, 2009 at 5:12 PM, chaitanya mehandru wrote: > Just for your info, I have been using ekiga 3.0.2 on Ubuntu hardy and I can > connect using - sip:abc at w.x.y.z. > I hear busy tone,connecting tone & ringing tone. > > On Fri, Feb 27, 2009 at 2:29 PM, Patrick Lee > wrote: >> >> are you suggesting "sip:hostname at dest_IP" >> where "hostname" can be anything and "dest_IP" is the remote endpoint >> IP address ? >> >> I tried "sip:abc at 192.168.1.34", it returned nothing, no connecting >> tone nor busying tone >> _______________________________________________ >> 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 Jim.Diamond at acadiau.ca Fri Feb 27 12:56:27 2009 From: Jim.Diamond at acadiau.ca (Jim Diamond) Date: Fri, 27 Feb 2009 08:56:27 -0400 Subject: [Ekiga-list] direct IP to IP SIP call without SIP registrar, not working in 3.x In-Reply-To: References: <6653d8470902262012g6ad8a1f6i3899301733ae146c@mail.gmail.com> Message-ID: <20090227125627.GA26790@tux.acadiau.ca> On Fri, Feb 27, 2009 at 07:37 (-0000), Dave Higton wrote: > Patrick Lee wrote: >> Not sure any one has asked this question before. >> I was able to make call without registering any SIP registrar in Ekiga >> ver 2.x. No need to create SIP account. >> Just type "sip:192.168.1.34" (the remote IP address) and the >> call was setup. >> And the remote client could be x-lite. >> But NOT with ver 3.x, the same syntax gave me no response. It seems >> like I have to create a SIP account first. >> My environment is a complete isolated network so I simply can't >> register in ekiga.net for SIP account. >> And there is some other SIP clients so I have to stick with >> SIP protocol. >> I know SIP registration is a proper SIP operation. But I love ekiga >> as it allows pt-to-pt call without setting up a SIP server. But not >> true for ver 3.x. Any solution ? > It may be worth mentioning that I have the same situation (no SIP > access to the outside world, therefore Ekiga cannot possibly > register to anything), the same requirement to do VoIP across our > own LAN (only), and the same problem. Dave, Have you tried connecting to h323:192.168.1.34 (or IP as appropriate)? It works for me both on a LAN and over a wan with 3.0.[12] and 3.1.0. Regrettably, I have other show-stopper problems, but that's another thread. Patrick, you say you have other SIP clients, but will the h323: thing work for you in your ekiga-to-ekiga work? Jim From sevmek at free.fr Fri Feb 27 14:57:19 2009 From: sevmek at free.fr (yannick) Date: Fri, 27 Feb 2009 15:57:19 +0100 Subject: [Ekiga-list] direct IP to IP SIP call without SIP registrar, not working in 3.x In-Reply-To: <20090227125627.GA26790@tux.acadiau.ca> References: <6653d8470902262012g6ad8a1f6i3899301733ae146c@mail.gmail.com> <20090227125627.GA26790@tux.acadiau.ca> Message-ID: <1235746639.15492.22.camel@achille> Le vendredi 27 f?vrier 2009 ? 08:56 -0400, Jim Diamond a ?crit : > >> I know SIP registration is a proper SIP operation. But I love > ekiga > >> as it allows pt-to-pt call without setting up a SIP server. But > not > >> true for ver 3.x. Any solution ? I reshaped our wiki page about NATs, did you read this troubleshooting? http://wiki.ekiga.org/index.php/Ekiga_behind_a_NAT_router#I_have_2_Ekiga_behind_a_NAT_using_STUN:_they_can.27t_communicate And this configuration setup if you're sure to only use Ekiga exclusively inside the LAN: http://wiki.ekiga.org/index.php/Ekiga_behind_a_NAT_router#How_to_disable_STUN_with_Ekiga_3.3F @Damien, What is the command line to enable STUN back using Ekiga 3.x? From sevmek at free.fr Fri Feb 27 15:02:56 2009 From: sevmek at free.fr (yannick) Date: Fri, 27 Feb 2009 16:02:56 +0100 Subject: [Ekiga-list] PTLIB alsa plugin status In-Reply-To: <49A7A650.3080805@gmail.com> References: <49A3BA0B.3010805@gmail.com> <49A3C7DF.1060400@gmail.com> <49A4FC57.1050104@gmail.com> <49A5CEC2.6090206@gmail.com> <49A6553D.9000301@gmail.com> <49A7260D.8020705@gmail.com> <49A7A650.3080805@gmail.com> Message-ID: <1235746976.15492.26.camel@achille> Le vendredi 27 f?vrier 2009 ? 09:37 +0100, Alec Leamas a ?crit : > Derek Smithies wrote: > > Hi, > > > > On Fri, 27 Feb 2009, Alec Leamas wrote: > > > >> Hm... a write operation could be guaranteed to return in finite time > >> (using non-blocking io + snd_pcm_wait). So couldn't the close method > >> just mark the chanell as closing, leaving the dirty work to the > >> "writer" thread and thus avoiding the locks? (Which, otoh, really > >> isn't a big issue in this scenario). If required, opening could be > >> handled in the same way, I guess. This would also create the > >> advantage that the thread could process the jitter buffer data in > >> parallel with the alsa output, without the need to wait for the IO to > >> complete. Wouldn't this give a more accurate timing? Also, avoiding > >> blocking io is a Good Thing IMHO. > > > > No. > > It must be a blocking write. The architecture of opal demands this. > > > > The play thread (using play as an example) repeatedly does the following > > read rtp packet from jitter buffer > > decode > > put raw audio to sound device (which delays for up to framesize of > > packet) > > > I didn't really make my point clear, sorry. I understand that the write > method should block, and my code does this, it's just a question how > it's implemented. Refactored to a write method: > > write( pcm, chunk) > if( closing) > close(); return(); > > snd_pcm_wait( pcm, timeout) > // Blocks until there is a free frame in alsa buffer, > // the same time as a blocking write would, using the > // the same "timer", but with a timeout option. > > if( timeout) > // Underrun? Check status & handle error. > else > write( pcm, chunk) // non-blocking > > > The basic difference is that this code will never block indefinitely - > thus making it it possible to remove the locks. Depending on the > blocking, alsa write implementation it might also give a slightly better > timing. But I shouldn't count on it. > I've no clue if this documentation might help, still the pulse audio main author refers it as "a guide": http://0pointer.de/blog/projects/guide-to-sound-apis.html Especially the section "You want to know more about the safe ALSA subset?" > > > > There was a time when pwlib and openh323 (the old names of ptlib and > > opal) > > used non blocking writes to the sound card plus software timers. the > > software timers were found to not be reliable enough to delay the > > write thread. Sometimes the delay was hundreds of milliseconds. So > > openh323 and pwlib were changed to use blocking writes, which gave > > much better audio performance. > > > > to change the operation of the write to be non blocking would have > > major architectural implications to opal. Let me help you. This won't > > happen. > Agreed > > Coming back to the other issues. Unfortunately, I'm the victim of > https://bugzilla.redhat.com/show_bug.cgi?id=481722, having a hard time > to to test Ekiga. I'll do what I can, though. > > _______________________________________________ > 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 Fri Feb 27 15:24:03 2009 From: dsandras at seconix.com (Damien Sandras) Date: Fri, 27 Feb 2009 16:24:03 +0100 Subject: [Ekiga-list] direct IP to IP SIP call without SIP registrar, not working in 3.x In-Reply-To: <1235746639.15492.22.camel@achille> References: <6653d8470902262012g6ad8a1f6i3899301733ae146c@mail.gmail.com> <20090227125627.GA26790@tux.acadiau.ca> <1235746639.15492.22.camel@achille> Message-ID: <1235748243.4012.25.camel@scorpion.multitel.be> Le vendredi 27 f?vrier 2009 ? 15:57 +0100, yannick a ?crit : > Le vendredi 27 f?vrier 2009 ? 08:56 -0400, Jim Diamond a ?crit : > > >> I know SIP registration is a proper SIP operation. But I love > > ekiga > > >> as it allows pt-to-pt call without setting up a SIP server. But > > not > > >> true for ver 3.x. Any solution ? > > I reshaped our wiki page about NATs, > > did you read this troubleshooting? > > http://wiki.ekiga.org/index.php/Ekiga_behind_a_NAT_router#I_have_2_Ekiga_behind_a_NAT_using_STUN:_they_can.27t_communicate > > And this configuration setup if you're sure to only use Ekiga > exclusively inside the LAN: > > http://wiki.ekiga.org/index.php/Ekiga_behind_a_NAT_router#How_to_disable_STUN_with_Ekiga_3.3F > > @Damien, > What is the command line to enable STUN back using Ekiga 3.x? gconftool-2 -s /apps/ekiga/general/nat/stun_server stun.ekiga.net --type=string This is only needed in 3.0 because in 3.20, there is a new option in the preferences window. -- _ 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 Feb 27 15:53:42 2009 From: dsandras at seconix.com (Damien Sandras) Date: Fri, 27 Feb 2009 16:53:42 +0100 Subject: [Ekiga-list] [ekiga engine] api availability and documentation In-Reply-To: <20090227075422.C0C4E10E7@mailweb.gpi.it> References: <20090227075422.C0C4E10E7@mailweb.gpi.it> Message-ID: <1235750022.4012.27.camel@scorpion.multitel.be> Le vendredi 27 f?vrier 2009 ? 08:53 +0100, Giampaolo Armellin a ?crit : > I?ve read on Ekiga web site that the engine is available to be used in > other projects. Nevertheless, I couldn?t find any reference to a SDK, > API or documents. > > > > May anyone tell me where that information can be found? I'm not sure it is completely doxygenified, but you could try generating the help from the headers. -- _ 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 Feb 27 15:54:28 2009 From: dsandras at seconix.com (Damien Sandras) Date: Fri, 27 Feb 2009 16:54:28 +0100 Subject: [Ekiga-list] call failure In-Reply-To: <1262408424.101235728337933.JavaMail.open-xchange@sam> References: <1497515573.61235644107546.JavaMail.open-xchange@sam> <49A6B598.3020305@pu-pm.univ-fcomte.fr> <1262408424.101235728337933.JavaMail.open-xchange@sam> Message-ID: <1235750068.4012.29.camel@scorpion.multitel.be> Le vendredi 27 f?vrier 2009 ? 20:52 +1100, Michael Stockenhuber a ?crit : > Hi, > I have replied and sent the logs but they are too big and wait for > moderator approval. It won't get approved, there are too many subscribers to this list. Please post it to pastebin. However, I doubt a gdb backtrace is that big. -- _ 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 Feb 27 15:55:11 2009 From: dsandras at seconix.com (Damien Sandras) Date: Fri, 27 Feb 2009 16:55:11 +0100 Subject: [Ekiga-list] WG: Connect to a LifeSize HD System In-Reply-To: References: Message-ID: <1235750111.4012.31.camel@scorpion.multitel.be> Le jeudi 26 f?vrier 2009 ? 09:11 +0100, Stefan Stoedtgen a ?crit : > Hi Ekiga List! > > I'm using Ekiga 3.0.2 stable under Windows XP, SP2 with a logitech > QuickCam. > I tried to connect to a LifeSize Room HD Conferencing Unit > (www.lifesize.com) which uses SIP and H323 > for communication. > > The connection seems to be established, but then, it breaks down. I > attached you the error.log. > Can you help me with this problem? Thanks for your Support! Breakdown = crash ? Because I see nothing wrong. Perhaps you should try H.323. -- _ 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 Feb 27 15:57:15 2009 From: dsandras at seconix.com (Damien Sandras) Date: Fri, 27 Feb 2009 16:57:15 +0100 Subject: [Ekiga-list] Incoming call failure with 3.1.1 In-Reply-To: <49A6611E.6040001@gmail.com> References: <87iqn7t2io.fsf@ixod.org> <1235062650.23177.8.camel@scorpion.multitel.be> <87ab8aosz1.fsf@ixod.org> <1235638756.4073.14.camel@scorpion.multitel.be> <49A6611E.6040001@gmail.com> Message-ID: <1235750235.4012.33.camel@scorpion.multitel.be> Le jeudi 26 f?vrier 2009 ? 10:30 +0100, Alec Leamas a ?crit : > Damien Sandras wrote: > > Le mercredi 25 f?vrier 2009 ? 21:02 -0500, Mark T.B. Carroll a ?crit : > > > >> Damien Sandras writes: > >> > >> > >>> Le jeudi 19 f?vrier 2009 ? 00:32 -0500, Mark T.B. Carroll a ?crit : > >>> > >>>> I have run through the configuration assistant thing from start to > >>>> finish. I can call the 500 at ekiga.net echo test and that works just fine. > >>>> However, calling the 520 at ekiga.net callback service has it hang up on me > >>>> and then ... nothing, though the -d 5 output shows that it is indeed > >>>> getting a callback initiated from from sip:500 at ekiga.net which is then > >>>> aborted. I am behind NAT and the router forwards incoming UDP from port > >>>> 5060 to 5100 to the machine I'm using and acts as a gateway to let all > >>>> my outgoing packets out. > >>>> > >>>> Should I gzip my -d 4 output and send it to somebody? I can also sniff > >>>> packets and send pcap files. I use Debian; software versions are, > >>>> > >>> There is a known problem with incoming calls and the current snapshot. I > >>> will fix it this week-end. > >>> > >> Now with the 20090225 one, the incoming call does arrive (yay!), I hit > >> `accept', and it segfaults. > >> > >> I can still send my -d 4 output to somebody. (-: > >> > > > > A gdb backtrace would be more useful. > > > > waiting for some kind of customer "service", taking a backtrace (yes, > same problem, trunk as of yesterday). Despite trying 50 times, I can not reproduce it. Are you sure something is not corrupted? Eugen, can you reproduce 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 mtbc at ixod.org Fri Feb 27 16:00:57 2009 From: mtbc at ixod.org (Mark T.B. Carroll) Date: Fri, 27 Feb 2009 11:00:57 -0500 Subject: [Ekiga-list] Documentation on NAT UDP timeouts Message-ID: <87tz6flvie.fsf@ixod.org> http://wiki.ekiga.org/index.php/Ekiga_behind_a_NAT_router#I_can_make_calls.2C_but_if_I_let_Ekiga_running_after_some_time_I_can.27t_receive_any_calls mentions, ip_conntrack_udp_timeout ip_conntrack_udp_timeout_stream but sysctl from a 2.6.26 kernel instead has, net.netfilter.nf_conntrack_udp_timeout = 30 net.netfilter.nf_conntrack_udp_timeout_stream = 180 net.ipv4.netfilter.ip_conntrack_udp_timeout = 30 net.ipv4.netfilter.ip_conntrack_udp_timeout_stream = 180 which I'm guessing are what I have to adjust on my system. (Changing the first pair seems to automatically change the second.) I'm having difficulty finding any setting in trunk's Ekiga GUI or gconf stuff corresponding to `you can configure each account to refresh the registration every 180 seconds'. Mark From dsandras at seconix.com Fri Feb 27 16:01:05 2009 From: dsandras at seconix.com (Damien Sandras) Date: Fri, 27 Feb 2009 17:01:05 +0100 Subject: [Ekiga-list] ekiga-snapshot-config-tool Debian packaging looks for wrong schema file In-Reply-To: <49A6AC0C.10402@pu-pm.univ-fcomte.fr> References: <87ocwyqw5o.fsf@ixod.org> <49A6AC0C.10402@pu-pm.univ-fcomte.fr> Message-ID: <1235750465.4012.35.camel@scorpion.multitel.be> Le jeudi 26 f?vrier 2009 ? 15:49 +0100, Eugen Dedu a ?crit : > Mark T.B. Carroll wrote: > > ekiga-snapshot-config-tool --install-schemas gives, > > > > I/O warning : failed to load external entity "/etc/gconf/schemas/ekiga.schemas" > > Failed to open `/etc/gconf/schemas/ekiga.schemas': No such file or directory > > > > My version of the ekiga-snapshot Debian package is 0-20090214-1 which > > instead has a /usr/share/gconf/schemas/ekiga-snapshot.schemas file. > > upstream, please apply the patch attached. > > Do you think it is still useful to distribute this small script? Is it > better to just inform people about the gconftool command line to remove > their ekiga configuration? I applied all your patches. I can't really answer your question because I don't have a precise opinion about this. -- _ 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 Jim.Diamond at acadiau.ca Fri Feb 27 16:07:04 2009 From: Jim.Diamond at acadiau.ca (Jim Diamond) Date: Fri, 27 Feb 2009 12:07:04 -0400 Subject: [Ekiga-list] ekiga-snapshot-config-tool Debian packaging looks for wrong schema file In-Reply-To: <1235750465.4012.35.camel@scorpion.multitel.be> References: <87ocwyqw5o.fsf@ixod.org> <49A6AC0C.10402@pu-pm.univ-fcomte.fr> <1235750465.4012.35.camel@scorpion.multitel.be> Message-ID: <20090227160704.GA960@tux.acadiau.ca> On Fri, Feb 27, 2009 at 17:01 (+0100), Damien Sandras wrote: > Le jeudi 26 f?vrier 2009 ? 15:49 +0100, Eugen Dedu a ?crit : >> Mark T.B. Carroll wrote: >>> ekiga-snapshot-config-tool --install-schemas gives, >>> I/O warning : failed to load external entity "/etc/gconf/schemas/ekiga.schemas" >>> Failed to open `/etc/gconf/schemas/ekiga.schemas': No such file or directory >>> My version of the ekiga-snapshot Debian package is 0-20090214-1 which >>> instead has a /usr/share/gconf/schemas/ekiga-snapshot.schemas file. >> upstream, please apply the patch attached. >> Do you think it is still useful to distribute this small script? Is it >> better to just inform people about the gconftool command line to remove >> their ekiga configuration? > I applied all your patches. > I can't really answer your question because I don't have a precise > opinion about this. For those of us who don't use gnome and gconf, it is better to have some way other than the non-existent gconftool. Cheers. Jim From nikos.alexandris at uranus.uni-freiburg.de Fri Feb 27 16:13:53 2009 From: nikos.alexandris at uranus.uni-freiburg.de (Nikos Alexandris) Date: Fri, 27 Feb 2009 17:13:53 +0100 Subject: [Ekiga-list] Contacting admins at accounts@ekiga.net (?) Message-ID: <1235751233.10433.7.camel@vertical> Dear list, my apologies for the kind of off-topic post. I am trying to retrieve a forgotten password and either the "Forgot Password" Service does not send any replies to my address, or for some other reason they don't reach their destination. I've never successfully used Ekiga to be honest since some of the camera models I tried to attach in my old laptop where not cooperating with Ubuntu. Therefore I was stuck in Skype. Now I have a new machine with a built-in webcam which works out-of-the-box under Ubuntu II / 64-bit. If some admin follows this list, please could you help me to retrieve my _very_ old and forgotten password? I've already mailed at accounts_at_ekiga_dot_net but I suspect that there might be a (generic) problem with mails comming from @ekiga.net reaching my mailbox!? My apologies again. Thanks, Nikos -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: From Eugen.Dedu at pu-pm.univ-fcomte.fr Fri Feb 27 16:24:51 2009 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Fri, 27 Feb 2009 17:24:51 +0100 Subject: [Ekiga-list] ekiga-snapshot-config-tool Debian packaging looks for wrong schema file In-Reply-To: <20090227160704.GA960@tux.acadiau.ca> References: <87ocwyqw5o.fsf@ixod.org> <49A6AC0C.10402@pu-pm.univ-fcomte.fr> <1235750465.4012.35.camel@scorpion.multitel.be> <20090227160704.GA960@tux.acadiau.ca> Message-ID: <49A813D3.8060102@pu-pm.univ-fcomte.fr> Jim Diamond wrote: > On Fri, Feb 27, 2009 at 17:01 (+0100), Damien Sandras wrote: > >> Le jeudi 26 f?vrier 2009 ? 15:49 +0100, Eugen Dedu a ?crit : >>> Mark T.B. Carroll wrote: >>>> ekiga-snapshot-config-tool --install-schemas gives, > >>>> I/O warning : failed to load external entity "/etc/gconf/schemas/ekiga.schemas" >>>> Failed to open `/etc/gconf/schemas/ekiga.schemas': No such file or directory > >>>> My version of the ekiga-snapshot Debian package is 0-20090214-1 which >>>> instead has a /usr/share/gconf/schemas/ekiga-snapshot.schemas file. > >>> upstream, please apply the patch attached. > >>> Do you think it is still useful to distribute this small script? Is it >>> better to just inform people about the gconftool command line to remove >>> their ekiga configuration? > >> I applied all your patches. > >> I can't really answer your question because I don't have a precise >> opinion about this. > > For those of us who don't use gnome and gconf, it is better to have > some way other than the non-existent gconftool. The problem is that this script has 131 lines and replaces only about 5 lines of code (rm -rf $HOME/.gconf/...; gconf --shutdown etc.) But we will wait until everybody is ok with this removal. -- Eugen From cralbrecht at wbcl.org Fri Feb 27 16:33:05 2009 From: cralbrecht at wbcl.org (Craig Albrecht) Date: Fri, 27 Feb 2009 08:33:05 -0800 Subject: [Ekiga-list] Incoming call failure with 3.1.1 (Damien Sandras) In-Reply-To: References: Message-ID: <9C1F56968AA83E4C967A7778B07EB12F0FB4AA3BEC@EXVMBX018-3.exch018.msoutlookonline.net> Same problem here using Ubuntu Hardy and Wednesday's trunk on three separate computers. Incoming calls segfault every time on each 3.1.1 build. Outgoing calls are ok. 500 at ekiga.net echo test works but all incoming calls segfault. Craig Albrecht Taylor University Broadcasting Inc Indiana, USA -----Original Message----- From: ekiga-list-bounces at gnome.org [mailto:ekiga-list-bounces at gnome.org] On Behalf Of ekiga-list-request at gnome.org Sent: Friday, February 27, 2009 10:58 AM To: ekiga-list at gnome.org Subject: ekiga-list Digest, Vol 31, Issue 59 Send ekiga-list mailing list submissions to ekiga-list at gnome.org To subscribe or unsubscribe via the World Wide Web, visit http://mail.gnome.org/mailman/listinfo/ekiga-list or, via email, send a message with subject or body 'help' to ekiga-list-request at gnome.org You can reach the person managing the list at ekiga-list-owner at gnome.org When replying, please edit your Subject line so it is more specific than "Re: Contents of ekiga-list digest..." Today's Topics: 1. Re: direct IP to IP SIP call without SIP registrar, not working in 3.x (Jim Diamond) 2. Re: direct IP to IP SIP call without SIP registrar, not working in 3.x (yannick) 3. Re: PTLIB alsa plugin status (yannick) 4. Re: direct IP to IP SIP call without SIP registrar, not working in 3.x (Damien Sandras) 5. Re: [ekiga engine] api availability and documentation (Damien Sandras) 6. Re: call failure (Damien Sandras) 7. Re: WG: Connect to a LifeSize HD System (Damien Sandras) 8. Re: Incoming call failure with 3.1.1 (Damien Sandras) ---------------------------------------------------------------------- Message: 1 Date: Fri, 27 Feb 2009 08:56:27 -0400 From: Jim Diamond Subject: Re: [Ekiga-list] direct IP to IP SIP call without SIP registrar, not working in 3.x To: Ekiga mailing list Message-ID: <20090227125627.GA26790 at tux.acadiau.ca> Content-Type: text/plain; charset=us-ascii On Fri, Feb 27, 2009 at 07:37 (-0000), Dave Higton wrote: > Patrick Lee wrote: >> Not sure any one has asked this question before. >> I was able to make call without registering any SIP registrar in Ekiga >> ver 2.x. No need to create SIP account. >> Just type "sip:192.168.1.34" (the remote IP address) and the >> call was setup. >> And the remote client could be x-lite. >> But NOT with ver 3.x, the same syntax gave me no response. It seems >> like I have to create a SIP account first. >> My environment is a complete isolated network so I simply can't >> register in ekiga.net for SIP account. >> And there is some other SIP clients so I have to stick with >> SIP protocol. >> I know SIP registration is a proper SIP operation. But I love ekiga >> as it allows pt-to-pt call without setting up a SIP server. But not >> true for ver 3.x. Any solution ? > It may be worth mentioning that I have the same situation (no SIP > access to the outside world, therefore Ekiga cannot possibly > register to anything), the same requirement to do VoIP across our > own LAN (only), and the same problem. Dave, Have you tried connecting to h323:192.168.1.34 (or IP as appropriate)? It works for me both on a LAN and over a wan with 3.0.[12] and 3.1.0. Regrettably, I have other show-stopper problems, but that's another thread. Patrick, you say you have other SIP clients, but will the h323: thing work for you in your ekiga-to-ekiga work? Jim ------------------------------ Message: 2 Date: Fri, 27 Feb 2009 15:57:19 +0100 From: yannick Subject: Re: [Ekiga-list] direct IP to IP SIP call without SIP registrar, not working in 3.x To: Ekiga mailing list Message-ID: <1235746639.15492.22.camel at achille> Content-Type: text/plain; charset=utf-8 Le vendredi 27 f?vrier 2009 ? 08:56 -0400, Jim Diamond a ?crit : > >> I know SIP registration is a proper SIP operation. But I love > ekiga > >> as it allows pt-to-pt call without setting up a SIP server. But > not > >> true for ver 3.x. Any solution ? I reshaped our wiki page about NATs, did you read this troubleshooting? http://wiki.ekiga.org/index.php/Ekiga_behind_a_NAT_router#I_have_2_Ekiga_behind_a_NAT_using_STUN:_they_can.27t_communicate And this configuration setup if you're sure to only use Ekiga exclusively inside the LAN: http://wiki.ekiga.org/index.php/Ekiga_behind_a_NAT_router#How_to_disable_STUN_with_Ekiga_3.3F @Damien, What is the command line to enable STUN back using Ekiga 3.x? ------------------------------ Message: 3 Date: Fri, 27 Feb 2009 16:02:56 +0100 From: yannick Subject: Re: [Ekiga-list] PTLIB alsa plugin status To: Ekiga mailing list Message-ID: <1235746976.15492.26.camel at achille> Content-Type: text/plain; charset=utf-8 Le vendredi 27 f?vrier 2009 ? 09:37 +0100, Alec Leamas a ?crit : > Derek Smithies wrote: > > Hi, > > > > On Fri, 27 Feb 2009, Alec Leamas wrote: > > > >> Hm... a write operation could be guaranteed to return in finite time > >> (using non-blocking io + snd_pcm_wait). So couldn't the close method > >> just mark the chanell as closing, leaving the dirty work to the > >> "writer" thread and thus avoiding the locks? (Which, otoh, really > >> isn't a big issue in this scenario). If required, opening could be > >> handled in the same way, I guess. This would also create the > >> advantage that the thread could process the jitter buffer data in > >> parallel with the alsa output, without the need to wait for the IO to > >> complete. Wouldn't this give a more accurate timing? Also, avoiding > >> blocking io is a Good Thing IMHO. > > > > No. > > It must be a blocking write. The architecture of opal demands this. > > > > The play thread (using play as an example) repeatedly does the following > > read rtp packet from jitter buffer > > decode > > put raw audio to sound device (which delays for up to framesize of > > packet) > > > I didn't really make my point clear, sorry. I understand that the write > method should block, and my code does this, it's just a question how > it's implemented. Refactored to a write method: > > write( pcm, chunk) > if( closing) > close(); return(); > > snd_pcm_wait( pcm, timeout) > // Blocks until there is a free frame in alsa buffer, > // the same time as a blocking write would, using the > // the same "timer", but with a timeout option. > > if( timeout) > // Underrun? Check status & handle error. > else > write( pcm, chunk) // non-blocking > > > The basic difference is that this code will never block indefinitely - > thus making it it possible to remove the locks. Depending on the > blocking, alsa write implementation it might also give a slightly better > timing. But I shouldn't count on it. > I've no clue if this documentation might help, still the pulse audio main author refers it as "a guide": http://0pointer.de/blog/projects/guide-to-sound-apis.html Especially the section "You want to know more about the safe ALSA subset?" > > > > There was a time when pwlib and openh323 (the old names of ptlib and > > opal) > > used non blocking writes to the sound card plus software timers. the > > software timers were found to not be reliable enough to delay the > > write thread. Sometimes the delay was hundreds of milliseconds. So > > openh323 and pwlib were changed to use blocking writes, which gave > > much better audio performance. > > > > to change the operation of the write to be non blocking would have > > major architectural implications to opal. Let me help you. This won't > > happen. > Agreed > > Coming back to the other issues. Unfortunately, I'm the victim of > https://bugzilla.redhat.com/show_bug.cgi?id=481722, having a hard time > to to test Ekiga. I'll do what I can, though. > > _______________________________________________ > 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 ------------------------------ Message: 4 Date: Fri, 27 Feb 2009 16:24:03 +0100 From: Damien Sandras Subject: Re: [Ekiga-list] direct IP to IP SIP call without SIP registrar, not working in 3.x To: Ekiga mailing list Message-ID: <1235748243.4012.25.camel at scorpion.multitel.be> Content-Type: text/plain; charset=UTF-8 Le vendredi 27 f?vrier 2009 ? 15:57 +0100, yannick a ?crit : > Le vendredi 27 f?vrier 2009 ? 08:56 -0400, Jim Diamond a ?crit : > > >> I know SIP registration is a proper SIP operation. But I love > > ekiga > > >> as it allows pt-to-pt call without setting up a SIP server. But > > not > > >> true for ver 3.x. Any solution ? > > I reshaped our wiki page about NATs, > > did you read this troubleshooting? > > http://wiki.ekiga.org/index.php/Ekiga_behind_a_NAT_router#I_have_2_Ekiga_behind_a_NAT_using_STUN:_they_can.27t_communicate > > And this configuration setup if you're sure to only use Ekiga > exclusively inside the LAN: > > http://wiki.ekiga.org/index.php/Ekiga_behind_a_NAT_router#How_to_disable_STUN_with_Ekiga_3.3F > > @Damien, > What is the command line to enable STUN back using Ekiga 3.x? gconftool-2 -s /apps/ekiga/general/nat/stun_server stun.ekiga.net --type=string This is only needed in 3.0 because in 3.20, there is a new option in the preferences window. -- _ 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 ------------------------------ Message: 5 Date: Fri, 27 Feb 2009 16:53:42 +0100 From: Damien Sandras Subject: Re: [Ekiga-list] [ekiga engine] api availability and documentation To: garmellin at gpi.it, Ekiga mailing list Message-ID: <1235750022.4012.27.camel at scorpion.multitel.be> Content-Type: text/plain; charset=UTF-8 Le vendredi 27 f?vrier 2009 ? 08:53 +0100, Giampaolo Armellin a ?crit : > I?ve read on Ekiga web site that the engine is available to be used in > other projects. Nevertheless, I couldn?t find any reference to a SDK, > API or documents. > > > > May anyone tell me where that information can be found? I'm not sure it is completely doxygenified, but you could try generating the help from the headers. -- _ 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 ------------------------------ Message: 6 Date: Fri, 27 Feb 2009 16:54:28 +0100 From: Damien Sandras Subject: Re: [Ekiga-list] call failure To: Ekiga mailing list Message-ID: <1235750068.4012.29.camel at scorpion.multitel.be> Content-Type: text/plain; charset=UTF-8 Le vendredi 27 f?vrier 2009 ? 20:52 +1100, Michael Stockenhuber a ?crit : > Hi, > I have replied and sent the logs but they are too big and wait for > moderator approval. It won't get approved, there are too many subscribers to this list. Please post it to pastebin. However, I doubt a gdb backtrace is that big. -- _ 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 ------------------------------ Message: 7 Date: Fri, 27 Feb 2009 16:55:11 +0100 From: Damien Sandras Subject: Re: [Ekiga-list] WG: Connect to a LifeSize HD System To: Ekiga mailing list Message-ID: <1235750111.4012.31.camel at scorpion.multitel.be> Content-Type: text/plain; charset=UTF-8 Le jeudi 26 f?vrier 2009 ? 09:11 +0100, Stefan Stoedtgen a ?crit : > Hi Ekiga List! > > I'm using Ekiga 3.0.2 stable under Windows XP, SP2 with a logitech > QuickCam. > I tried to connect to a LifeSize Room HD Conferencing Unit > (www.lifesize.com) which uses SIP and H323 > for communication. > > The connection seems to be established, but then, it breaks down. I > attached you the error.log. > Can you help me with this problem? Thanks for your Support! Breakdown = crash ? Because I see nothing wrong. Perhaps you should try H.323. -- _ 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 ------------------------------ Message: 8 Date: Fri, 27 Feb 2009 16:57:15 +0100 From: Damien Sandras Subject: Re: [Ekiga-list] Incoming call failure with 3.1.1 To: Ekiga mailing list Message-ID: <1235750235.4012.33.camel at scorpion.multitel.be> Content-Type: text/plain; charset=UTF-8 Le jeudi 26 f?vrier 2009 ? 10:30 +0100, Alec Leamas a ?crit : > Damien Sandras wrote: > > Le mercredi 25 f?vrier 2009 ? 21:02 -0500, Mark T.B. Carroll a ?crit : > > > >> Damien Sandras writes: > >> > >> > >>> Le jeudi 19 f?vrier 2009 ? 00:32 -0500, Mark T.B. Carroll a ?crit : > >>> > >>>> I have run through the configuration assistant thing from start to > >>>> finish. I can call the 500 at ekiga.net echo test and that works just fine. > >>>> However, calling the 520 at ekiga.net callback service has it hang up on me > >>>> and then ... nothing, though the -d 5 output shows that it is indeed > >>>> getting a callback initiated from from sip:500 at ekiga.net which is then > >>>> aborted. I am behind NAT and the router forwards incoming UDP from port > >>>> 5060 to 5100 to the machine I'm using and acts as a gateway to let all > >>>> my outgoing packets out. > >>>> > >>>> Should I gzip my -d 4 output and send it to somebody? I can also sniff > >>>> packets and send pcap files. I use Debian; software versions are, > >>>> > >>> There is a known problem with incoming calls and the current snapshot. I > >>> will fix it this week-end. > >>> > >> Now with the 20090225 one, the incoming call does arrive (yay!), I hit > >> `accept', and it segfaults. > >> > >> I can still send my -d 4 output to somebody. (-: > >> > > > > A gdb backtrace would be more useful. > > > > waiting for some kind of customer "service", taking a backtrace (yes, > same problem, trunk as of yesterday). Despite trying 50 times, I can not reproduce it. Are you sure something is not corrupted? Eugen, can you reproduce 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 ------------------------------ _______________________________________________ ekiga-list mailing list ekiga-list at gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list End of ekiga-list Digest, Vol 31, Issue 59 ****************************************** From leamas.alec at gmail.com Fri Feb 27 18:21:13 2009 From: leamas.alec at gmail.com (Alec Leamas) Date: Fri, 27 Feb 2009 19:21:13 +0100 Subject: [Ekiga-list] PTLIB alsa plugin status In-Reply-To: References: <49A3BA0B.3010805@gmail.com> <49A3C7DF.1060400@gmail.com> <49A4FC57.1050104@gmail.com> <49A5CEC2.6090206@gmail.com> <49A6553D.9000301@gmail.com> <49A7260D.8020705@gmail.com> Message-ID: <49A82F19.4090807@gmail.com> Derek Smithies wrote: > [ cut, replied earlier today...] > > >>> I don't think this aspect of the the Opal design is a problem. The >>> problem we are are trying to address is the reason for the buffering >>> - why is there a 100ms delay??? >> Yes. I *think* I've seen five periods hardcoded somewhere... First of all: an overview. You state that the the hw buffering should be two periods, each period 30 or possibly 20 ms. You havn't mentioned sample rate(?), I assume for the moment that we agree on 8 kHz. This would be the interface between the codcc and the sound_alsa stuff. The 20/30 ms is a requirement from the codecs, implemented by the alsa read/write methods. Andrea has debug printouts from the settings when doing a voice call, see the thread "A comparisom ALSA-PULSE" a few days ago. Basically, this boils down to 8Khz, period size 160 frames == 20ms, hw buffer size = 800 frames = 5 periods == 100 ms. This is the sound_alsa /pulse emulated alsa interface settings. The buffer is way to large. And when I take a new look today by making a cat of the /proc/asound files I find rate: 44100, period_size: 8192 == 18.5 ms buffer_size: 16384 == 37 ms. This is the real stuff, the way pulse handles the alsa device. Bottom up: I'm not worried about the 44.1 kHz. Pulse is designed to convert our 8kHz stream to a 44.1 kHz one without any problems. But we should be aware of that what we see in /proc/asound is what pulse sets up against the hw; our settings vs pulse is another issue. I missed that. sound_alsa.cxx/pulse: I really need to look into the code here.... Here are a lot of hardcoded values, no symbolic constants... seems that the buffer is initially 4 periods (storedPeriods is initiated to 4). The setBuffer calls changes storedPeriods and thus buffer size - at a glance the code looks OK. So: a simple PTRACE in SetBuffers should reveal how the buffers are set. For the moment, I presume that this is how the codec's requirement on a specific sample rate is implemented. I need a whisky. Later on, I'll try refine the documentation for PsoundChannel. > > >>> Answer: >>> There are two entities that I have seen which can "store" audio to >>> give you a delay. >>> The jitter buffer, which can store seconds of audio. >>> There are status variables in the jitter buffer which indicate how >>> long it is buffering audio for. >> As I suspected. Thanks also for this. So basically we have network >> latency, jitter/echo cancellation buffer and the device/alsa buffer, >> all in total preferably in the 150 - 200 ms range. If there is no >> echo cancellation, the alsa buffer (if larger) could also be jitter >> buffer. But not if fancy things like echo cancellation should be >> performed (?). > You may have the answer here. > How much delay does the speex echo cancellor introduce ? No idea. Anyone, out here? But we seem to have is a 100 ms alsa hw buffer, which will be added to any other buffers involved, including the echo cancellation buffer. > >>> it is defaulted to.. >> The thing is that when looking at the alsa device from the operating >> system level (in the /proc filesystem) it's clear that the buffer is >> 5 periods * 20 ms = 100 ms (details in the thread initiated by >> Andrea). So something is not as expected... Is the simple truth that >> the alsa period size doesn't match the codec chunk size? But even >> if so, should it matter? "suspicious" > > Alsa probably introduces a delay/buffering of its own when you do > alsa<-->pulse conversions. > > Can you repeat the above test on an older distro where the machine > does not have pulse? Havn't any, and I havn't had any luck using sound in my VirtualBox VM:s either :-( > > > Derek. --a From cralbrecht at wbcl.org Fri Feb 27 18:51:19 2009 From: cralbrecht at wbcl.org (Craig Albrecht) Date: Fri, 27 Feb 2009 10:51:19 -0800 Subject: [Ekiga-list] Incoming call failure with 3.1.1 (Damien Sandras) In-Reply-To: References: Message-ID: <9C1F56968AA83E4C967A7778B07EB12F0FB4AA3C68@EXVMBX018-3.exch018.msoutlookonline.net> Just tried today's trunk. Still segfault on all inbound calls on fully updated Ubuntu Hardy using these build instructions: http://wiki.ekiga.org/index.php/Compile_your_own_SVN_version_of_Ekiga_on_Ubuntu Is this method still accurate? A build created last week (or was it earlier this week? Cant remember) using this method would not indicate the presence of incoming call but outgoing call worked. Today's trunk indicates incoming call, but get immediate segfault when clicking "accept." What I am hoping for is a working build that includes the celt ultra-low delay codec. I do have 0.5.2 celt installed since opal wouldn't configure with celt enabled unless I previously install celt on the computer. Craig Albrecht WBCL Radio Network Fort Wayne, Indiana USA Taylor University From sevmek at free.fr Fri Feb 27 18:52:14 2009 From: sevmek at free.fr (yannick) Date: Fri, 27 Feb 2009 19:52:14 +0100 Subject: [Ekiga-list] Contacting admins at accounts@ekiga.net (?) In-Reply-To: <1235751233.10433.7.camel@vertical> References: <1235751233.10433.7.camel@vertical> Message-ID: <1235760734.15492.32.camel@achille> Le vendredi 27 f?vrier 2009 ? 17:13 +0100, Nikos Alexandris a ?crit : > Dear list, > > my apologies for the kind of off-topic post. I am trying to retrieve a > forgotten password and either the "Forgot Password" Service does not > send any replies to my address, or for some other reason they don't > reach their destination. > Hi, I coded the ekiga.net web interface. I just tested the forgot password service and it works with my address. I suspect something between ekiga.net server and your mail box blocks the email. (maybe a antispam service?). If you give me your username, i'll post a mail directly to you with your password. Best regards, Yannick > I've never successfully used Ekiga to be honest since some of the camera > models I tried to attach in my old laptop where not cooperating with > Ubuntu. Therefore I was stuck in Skype. > > Now I have a new machine with a built-in webcam which works > out-of-the-box under Ubuntu II / 64-bit. > > If some admin follows this list, please could you help me to retrieve my > _very_ old and forgotten password? I've already mailed at > accounts_at_ekiga_dot_net but I suspect that there might be a (generic) > problem with mails comming from @ekiga.net reaching my mailbox!? > > My apologies again. Thanks, Nikos > _______________________________________________ > 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 sevmek at free.fr Fri Feb 27 18:53:40 2009 From: sevmek at free.fr (yannick) Date: Fri, 27 Feb 2009 19:53:40 +0100 Subject: [Ekiga-list] direct IP to IP SIP call without SIP registrar, not working in 3.x In-Reply-To: <1235748243.4012.25.camel@scorpion.multitel.be> References: <6653d8470902262012g6ad8a1f6i3899301733ae146c@mail.gmail.com> <20090227125627.GA26790@tux.acadiau.ca> <1235746639.15492.22.camel@achille> <1235748243.4012.25.camel@scorpion.multitel.be> Message-ID: <1235760820.15492.34.camel@achille> Le vendredi 27 f?vrier 2009 ? 16:24 +0100, Damien Sandras a ?crit : > Le vendredi 27 f?vrier 2009 ? 15:57 +0100, yannick a ?crit : > > Le vendredi 27 f?vrier 2009 ? 08:56 -0400, Jim Diamond a ?crit : > > > >> I know SIP registration is a proper SIP operation. But I love > > > ekiga > > > >> as it allows pt-to-pt call without setting up a SIP server. But > > > not > > > >> true for ver 3.x. Any solution ? > > > > I reshaped our wiki page about NATs, > > > > did you read this troubleshooting? > > > > http://wiki.ekiga.org/index.php/Ekiga_behind_a_NAT_router#I_have_2_Ekiga_behind_a_NAT_using_STUN:_they_can.27t_communicate > > > > And this configuration setup if you're sure to only use Ekiga > > exclusively inside the LAN: > > > > http://wiki.ekiga.org/index.php/Ekiga_behind_a_NAT_router#How_to_disable_STUN_with_Ekiga_3.3F > > > > @Damien, > > What is the command line to enable STUN back using Ekiga 3.x? > > gconftool-2 -s /apps/ekiga/general/nat/stun_server stun.ekiga.net > --type=string > > This is only needed in 3.0 because in 3.20, there is a new option in the > preferences window. Ok, thx. From nikos.alexandris at uranus.uni-freiburg.de Fri Feb 27 19:49:04 2009 From: nikos.alexandris at uranus.uni-freiburg.de (Nikos Alexandris) Date: Fri, 27 Feb 2009 20:49:04 +0100 Subject: [Ekiga-list] Contacting admins at accounts@ekiga.net (?) In-Reply-To: <1235760734.15492.32.camel@achille> References: <1235751233.10433.7.camel@vertical> <1235760734.15492.32.camel@achille> Message-ID: <1235764144.14870.0.camel@vertical> Just a thank you to Yannick for his support. I am on-line :-) Cheers, Nikos -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: From leamas.alec at gmail.com Fri Feb 27 20:04:35 2009 From: leamas.alec at gmail.com (Alec Leamas) Date: Fri, 27 Feb 2009 21:04:35 +0100 Subject: [Ekiga-list] PTLIB alsa plugin status In-Reply-To: References: <49A3BA0B.3010805@gmail.com> <49A3C7DF.1060400@gmail.com> <49A4FC57.1050104@gmail.com> <49A5CEC2.6090206@gmail.com> <49A6553D.9000301@gmail.com> <49A7260D.8020705@gmail.com> Message-ID: <49A84753.6030601@gmail.com> About the sound_alsa::write: As of today, both PsoundChannel abstract definition and the method comment in psound_alsa mentions a writeTimeout, with the obvious functionality. However, this is not implemented by the actual code. So: something is wrong, but what? Code? comment? Or? Seems that sound_alsa::read has the same problem. --a From leamas.alec at gmail.com Fri Feb 27 20:10:03 2009 From: leamas.alec at gmail.com (Alec Leamas) Date: Fri, 27 Feb 2009 21:10:03 +0100 Subject: [Ekiga-list] PTLIB alsa plugin status In-Reply-To: <1235746976.15492.26.camel@achille> References: <49A3BA0B.3010805@gmail.com> <49A3C7DF.1060400@gmail.com> <49A4FC57.1050104@gmail.com> <49A5CEC2.6090206@gmail.com> <49A6553D.9000301@gmail.com> <49A7260D.8020705@gmail.com> <49A7A650.3080805@gmail.com> <1235746976.15492.26.camel@achille> Message-ID: <49A8489B.6030405@gmail.com> yannick wrote: > I've no clue if this documentation might help, still the pulse audio > main author refers it as "a guide": > http://0pointer.de/blog/projects/guide-to-sound-apis.html > > Especially the section "You want to know more about the safe ALSA > subset?" > > These kinds of hints are always welcome! And I can make us all happy when saying that both the current implementation and the changes discussed are within this safe set. --a From hs.samix at gmail.com Fri Feb 27 20:29:21 2009 From: hs.samix at gmail.com (H. S.) Date: Fri, 27 Feb 2009 15:29:21 -0500 Subject: [Ekiga-list] list manager: could we have this on gmane.org? Message-ID: Hello, This is intended for whoever is maintaining this mailing list. I was wondering if this list can be made available via gmane.org. That way people can read this list as newsgroup on nntp server of gmane as well (list subscription would still be required). I am new to this list and I am not sure if this has been requested or looked into before. Regards and thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: From derek at indranet.co.nz Fri Feb 27 20:36:27 2009 From: derek at indranet.co.nz (Derek Smithies) Date: Sat, 28 Feb 2009 09:36:27 +1300 (NZDT) Subject: [Ekiga-list] PTLIB alsa plugin status In-Reply-To: <1235746976.15492.26.camel@achille> References: <49A3BA0B.3010805@gmail.com> <49A3C7DF.1060400@gmail.com> <49A4FC57.1050104@gmail.com> <49A5CEC2.6090206@gmail.com> <49A6553D.9000301@gmail.com> <49A7260D.8020705@gmail.com> <49A7A650.3080805@gmail.com> <1235746976.15492.26.camel@achille> Message-ID: On Fri, 27 Feb 2009, yannick wrote: > I've no clue if this documentation might help, still the pulse audio > main author refers it as "a guide": > http://0pointer.de/blog/projects/guide-to-sound-apis.html > > Especially the section "You want to know more about the safe ALSA > subset?" This is a great link. There are some non optimal components in the alsa plugin, or rather, things that are not "safe". I have some sadness at this - the alsa plugin in ptlib was "copied" from the example they provided. Derek. -- Derek Smithies Ph.D. IndraNet Technologies Ltd. Email: derek at indranet.co.nz ph +64 3 365 6485 Web: http://www.indranet-technologies.com/ From derek at indranet.co.nz Fri Feb 27 20:40:42 2009 From: derek at indranet.co.nz (Derek Smithies) Date: Sat, 28 Feb 2009 09:40:42 +1300 (NZDT) Subject: [Ekiga-list] PTLIB alsa plugin status In-Reply-To: <49A82F19.4090807@gmail.com> References: <49A3BA0B.3010805@gmail.com> <49A3C7DF.1060400@gmail.com> <49A4FC57.1050104@gmail.com> <49A5CEC2.6090206@gmail.com> <49A6553D.9000301@gmail.com> <49A7260D.8020705@gmail.com> <49A82F19.4090807@gmail.com> Message-ID: Hi, On Fri, 27 Feb 2009, Alec Leamas wrote: > I need a whisky. Coffee is much better. Don't add any impurities though (milk, sugar etc) > Later on, I'll try refine the documentation for PsoundChannel. cool. Email any docs you have to me directly, and I will add them to the inline documentation in the ptlib sources. Derek. -- Derek Smithies Ph.D. IndraNet Technologies Ltd. Email: derek at indranet.co.nz ph +64 3 365 6485 Web: http://www.indranet-technologies.com/ From res3stockm at catalysis.at Fri Feb 27 22:28:26 2009 From: res3stockm at catalysis.at (Michael Stockenhuber) Date: Sat, 28 Feb 2009 09:28:26 +1100 (EST) Subject: [Ekiga-list] call failure In-Reply-To: <1235750068.4012.29.camel@scorpion.multitel.be> References: <1497515573.61235644107546.JavaMail.open-xchange@sam> <49A6B598.3020305@pu-pm.univ-fcomte.fr> <1262408424.101235728337933.JavaMail.open-xchange@sam> <1235750068.4012.29.camel@scorpion.multitel.be> Message-ID: <1902440710.161235773706113.JavaMail.open-xchange@sam> Hi, Fair enough. Its great to hear that there are a lot of users. It is not a gdb backtrace it the debug output from ekiga in linux ( ekiga -d 4). Anyway, I have cut out the stuff that was repeated a lot and got it down to below 40 kB. File is enclosed. Maybe someone can help. ? Cheers Michael On February 28, 2009 at 2:54 AM Damien Sandras wrote: > Le vendredi 27 f?vrier 2009 ? 20:52 +1100, Michael Stockenhuber a > ?crit : > > Hi, > > I have replied and sent the logs but they are too big and wait for > > moderator approval. > > It won't get approved, there are too many subscribers to this list. > Please post it to pastebin. However, I doubt a gdb backtrace is that > big. > -- >? _? ? ?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: -------------- next part -------------- A non-text attachment was scrubbed... Name: vista_reduced.txt.gz Type: application/gzip Size: 23701 bytes Desc: not available URL: From leepatricklee at gmail.com Sat Feb 28 06:01:46 2009 From: leepatricklee at gmail.com (Patrick Lee) Date: Sat, 28 Feb 2009 14:01:46 +0800 Subject: [Ekiga-list] direct IP to IP SIP call without SIP registrar, not working in 3.x In-Reply-To: <20090227125627.GA26790@tux.acadiau.ca> References: <6653d8470902262012g6ad8a1f6i3899301733ae146c@mail.gmail.com> <20090227125627.GA26790@tux.acadiau.ca> Message-ID: <6653d8470902272201s2c131cb4t380a3bb2da898bd4@mail.gmail.com> Actually there are some Tandberg endpoints in my LAN. Tandberg MXP 1700 - H323 and IP supported Tandberg E20 - SIP only In my network there is no NAT, actually some equipments are in the same subnet, i.e. no routing involved. With Ekiga 2.x, SIP connection with both Tandberg endpoints are ok, but the video codec supported is only H.261. With Ekiga 3.x, neither H323 nor SIP call was gone through. In my Tandberg box, no SIP service IP is configured. I was able to make a SIP from Ekiga 2.x to Tandberg. When the call is set up. Tandberg showed the caller SIP address is abc at w.x.y.z, where abc is my computer hostname and w.x.y.z is caller's IP. But call made from Tandberg to ekiga failed. Interesting...... I did the test particularly on SIP. For H.323 I can use Netmeeting, which is pretty stable. And all I have to find out whether two SIP clients can talk with each other without registering to SIP server. Otherwise I need a separate SIP server module running in my LAN. From law_ence.dev at ntlworld.com Sat Feb 28 11:57:51 2009 From: law_ence.dev at ntlworld.com (ael) Date: Sat, 28 Feb 2009 11:57:51 +0000 Subject: [Ekiga-list] list manager: could we have this on gmane.org? In-Reply-To: References: Message-ID: <49A926BF.8020003@ntlworld.com> H. S. wrote: > Hello, > > This is intended for whoever is maintaining this mailing list. I was > wondering if this list can be made available via gmane.org. IIRC you simply make the request to gmane. So you are asking in the wrong place: instead visit the gmane website and enter the request. ael From leamas.alec at gmail.com Sat Feb 28 13:25:47 2009 From: leamas.alec at gmail.com (Alec Leamas) Date: Sat, 28 Feb 2009 14:25:47 +0100 Subject: [Ekiga-list] PTLIB alsa plugin status In-Reply-To: References: <49A3BA0B.3010805@gmail.com> <49A3C7DF.1060400@gmail.com> <49A4FC57.1050104@gmail.com> <49A5CEC2.6090206@gmail.com> <49A6553D.9000301@gmail.com> <49A7260D.8020705@gmail.com> <49A82F19.4090807@gmail.com> Message-ID: <49A93B5B.3090407@gmail.com> Derek Smithies wrote: > Hi, > > On Fri, 27 Feb 2009, Alec Leamas wrote: >> I need a whisky. > Coffee is much better. Don't add any impurities though (milk, sugar etc) I'm was actually using both whisky AND coffe w milk. Sorry, no offense... :-) After some serious fights w the build system, I've been able to add a simple PTRACE to the SetBuffers method in sound_alsa.cxx. Trimmed output: 13:45:49.348 ALSA Setting buffers, size: 3840, count: 5 13:45:49.402 ALSA Device default Opened 13:45:49.438 ALSA Setting buffers, size: 320, count: 5 which verifies Andreas' logs i. e., this is what causes the oversized alsa hw buffer. I made a quick search, there are no references to SetBuffers in the plugin code. So these calls comes from the upper layers. For the moment I'll stick to the alsa plugin and will not investigate this any further. From leamas.alec at gmail.com Sat Feb 28 15:04:19 2009 From: leamas.alec at gmail.com (Alec Leamas) Date: Sat, 28 Feb 2009 16:04:19 +0100 Subject: [Ekiga-list] call failure In-Reply-To: <1902440710.161235773706113.JavaMail.open-xchange@sam> References: <1497515573.61235644107546.JavaMail.open-xchange@sam> <49A6B598.3020305@pu-pm.univ-fcomte.fr> <1262408424.101235728337933.JavaMail.open-xchange@sam> <1235750068.4012.29.camel@scorpion.multitel.be> <1902440710.161235773706113.JavaMail.open-xchange@sam> Message-ID: <49A95273.6030903@gmail.com> I've been able to reproduce what I think is the same error (core dumped when 520 calls back). Gdb backtrace in http://mail.gnome.org/archives/ekiga-list/2009-February/msg00282.html --a Michael Stockenhuber wrote: > Hi, > > Fair enough. Its great to hear that there are a lot of users. > It is not a gdb backtrace it the debug output from ekiga in linux ( > ekiga -d 4). Anyway, I have cut out the stuff that was repeated a lot > and got it down to below 40 kB. File is enclosed. > Maybe someone can help. > > Cheers > > Michael > > > On February 28, 2009 at 2:54 AM Damien Sandras > wrote: > > > Le vendredi 27 f?vrier 2009 ? 20:52 +1100, Michael Stockenhuber a > > ?crit : > > > Hi, > > > I have replied and sent the logs but they are too big and wait for > > > moderator approval. > > > > It won't get approved, there are too many subscribers to this list. > > Please post it to pastebin. However, I doubt a gdb backtrace is that > > big. > > -- > > _ 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 From hs.samix at gmail.com Sat Feb 28 20:43:38 2009 From: hs.samix at gmail.com (H. S.) Date: Sat, 28 Feb 2009 15:43:38 -0500 Subject: [Ekiga-list] list manager: could we have this on gmane.org? In-Reply-To: <49A926BF.8020003@ntlworld.com> References: <49A926BF.8020003@ntlworld.com> Message-ID: On Sat, Feb 28, 2009 at 6:57 AM, ael wrote: > H. S. wrote: > >> Hello, >> >> This is intended for whoever is maintaining this mailing list. I was >> wondering if this list can be made available via gmane.org. >> > > IIRC you simply make the request to gmane. So you are asking in the wrong > place: instead visit the gmane website and enter the request. > > ael Aha! My bad then. I was under the impression a list manager has to allow gmane (or create and account there or some such thing) to mirror the list as a newsgroup. I will take a look at gmane.org. Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: From hs.samix at gmail.com Sat Feb 28 20:49:21 2009 From: hs.samix at gmail.com (H. S.) Date: Sat, 28 Feb 2009 15:49:21 -0500 Subject: [Ekiga-list] no incoming calls behing an ADSL modem Message-ID: Hi, I have just convinced a few of my friends to move from Skype to Ekiga. While testing with one of them, we noticed that he can call me sucessfully but I cannot call him. If I try calling his sip address, I get a message in the status "Remote user is unreachable". That user is behing a modem which is working in pppoe mode. His computer computer has a private address. While configure Ekiga, the stun was selected in the network setting. His computer is Ubuntu Hardy, Ekiga 2.0.12. How do we go about solving this problem? Thanks. PS: With echo cancellation off, the voice quality is at least as good as we get with Skype. Good job, ekiga devels! But with echo cancellation on, the quality is not as good. Proving that the suggestion in online docs to use headsets is a good once :) -------------- next part -------------- An HTML attachment was scrubbed... URL: From hs.samix at gmail.com Sat Feb 28 21:20:05 2009 From: hs.samix at gmail.com (H. S.) Date: Sat, 28 Feb 2009 16:20:05 -0500 Subject: [Ekiga-list] no incoming calls behing an ADSL modem In-Reply-To: References: Message-ID: On Sat, Feb 28, 2009 at 3:49 PM, H. S. wrote: > Hi, > > I have just convinced a few of my friends to move from Skype to Ekiga. > > While testing with one of them, we noticed that he can call me sucessfully > but I cannot call him. If I try calling his sip address, I get a message in > the status "Remote user is unreachable". That user is behing a modem which > is working in pppoe mode. His computer computer has a private address. While > configure Ekiga, the stun was selected in the network setting. His computer > is Ubuntu Hardy, Ekiga 2.0.12. > > How do we go about solving this problem? > > Thanks. > PS: With echo cancellation off, the voice quality is at least as good as we > get with Skype. Good job, ekiga devels! But with echo cancellation on, the > quality is not as good. Proving that the suggestion in online docs to use > headsets is a good once :) > hmm ... he restarted Ekiga and now I am able to call him, even across the pppoe ADSL modem. Looks like a restart of Ekiga fixed something. Does that show what could have been missed? Sorry for all the noise. Regards. -------------- next part -------------- An HTML attachment was scrubbed... URL: From derek at indranet.co.nz Sat Feb 28 22:51:31 2009 From: derek at indranet.co.nz (Derek Smithies) Date: Sun, 1 Mar 2009 11:51:31 +1300 (NZDT) Subject: [Ekiga-list] PTLIB alsa plugin status In-Reply-To: <49A93B5B.3090407@gmail.com> References: <49A3BA0B.3010805@gmail.com> <49A3C7DF.1060400@gmail.com> <49A4FC57.1050104@gmail.com> <49A5CEC2.6090206@gmail.com> <49A6553D.9000301@gmail.com> <49A7260D.8020705@gmail.com> <49A82F19.4090807@gmail.com> <49A93B5B.3090407@gmail.com> Message-ID: Hi, On Sat, 28 Feb 2009, Alec Leamas wrote: >> Coffee is much better. Don't add any impurities though (milk, sugar etc) > I'm was actually using both whisky AND coffe w milk. Sorry, no offense... > :-) No offense taken. I put that comment in to lighten the tone a little. > After some serious fights w the build system, I've been able to add a simple > PTRACE to the SetBuffers method in sound_alsa.cxx. Trimmed output: yeah - it is much easier to avoid such battles and put in cerr statements... These battles are a pain and a complete waste of time. They really really annoy me. Like, autoconf was supposed to remove hassle. It hasn't. The kernel does not use autoconf -- which suggests to me that autoconf is not all capable. The ptlib&opal build system consists of multiple projects that interdepend on each other. autoconf (ideally) requires us to duplicate code and directories, and separate the projects out. forget that. Derek. > Derek Smithies wrote: >> Hi, >> >> On Fri, 27 Feb 2009, Alec Leamas wrote: >>> I need a whisky. >> Coffee is much better. Don't add any impurities though (milk, sugar etc) > I'm was actually using both whisky AND coffe w milk. Sorry, no offense... > :-) > > > 13:45:49.348 ALSA Setting buffers, size: 3840, count: 5 > 13:45:49.402 ALSA Device default Opened > 13:45:49.438 ALSA Setting buffers, size: 320, count: 5 > > which verifies Andreas' logs i. e., this is what causes the oversized alsa > hw buffer. I made a quick search, there are no references to SetBuffers in > the plugin code. So these calls comes from the upper layers. For the moment > I'll stick to the alsa plugin and will not investigate this any further. > > > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > > -- Derek Smithies Ph.D. IndraNet Technologies Ltd. Email: derek at indranet.co.nz ph +64 3 365 6485 Web: http://www.indranet-technologies.com/ From derek at indranet.co.nz Sat Feb 28 23:12:10 2009 From: derek at indranet.co.nz (Derek Smithies) Date: Sun, 1 Mar 2009 12:12:10 +1300 (NZDT) Subject: [Ekiga-list] PTLIB alsa plugin status In-Reply-To: <49A93B5B.3090407@gmail.com> References: <49A3BA0B.3010805@gmail.com> <49A3C7DF.1060400@gmail.com> <49A4FC57.1050104@gmail.com> <49A5CEC2.6090206@gmail.com> <49A6553D.9000301@gmail.com> <49A7260D.8020705@gmail.com> <49A82F19.4090807@gmail.com> <49A93B5B.3090407@gmail.com> Message-ID: On Sat, 28 Feb 2009, Alec Leamas wrote: > Derek Smithies wrote: >> Hi, >> >> On Fri, 27 Feb 2009, Alec Leamas wrote: >>> I need a whisky. >> Coffee is much better. Don't add any impurities though (milk, sugar etc) > I'm was actually using both whisky AND coffe w milk. Sorry, no offense... > :-) > > After some serious fights w the build system, I've been able to add a simple > PTRACE to the SetBuffers method in sound_alsa.cxx. Trimmed output: > > 13:45:49.348 ALSA Setting buffers, size: 3840, count: 5 > 13:45:49.402 ALSA Device default Opened > 13:45:49.438 ALSA Setting buffers, size: 320, count: 5 It is set in opal in OpalAudioMediaStream::OpalAudioMediaStream( where soundChannelBuffers is set to the supplied parameter value. This comes out of the pcssendpoint class, which which ends up coming from: a method of the pcss endpoint which gets the user defined buffer depth... soundChannelBuffers = pcss endpoint.GetSoundChannelBufferDepth() so you know what ? I think this is a bug from outside of ptlib&opal. The default values for codec sizes in ptlib&opal are for a count of 2 buffers (unix) and 3 buffers(windows). Derek. > which verifies Andreas' logs i. e., this is what causes the oversized alsa > hw buffer. I made a quick search, there are no references to SetBuffers in > the plugin code. So these calls comes from the upper layers. For the moment > I'll stick to the alsa plugin and will not investigate this any further. > > > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > > -- Derek Smithies Ph.D. IndraNet Technologies Ltd. Email: derek at indranet.co.nz ph +64 3 365 6485 Web: http://www.indranet-technologies.com/