Re: [Ekiga-list] list manager: could we have this on gmane.org?
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 ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] PTLIB alsa plugin status
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 ALSASetting buffers, size: 3840, count: 5 13:45:49.402 ALSADevice default Opened 13:45:49.438 ALSASetting 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@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] call failure
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 dsand...@seconix.com 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:dsand...@ekiga.net ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] list manager: could we have this on gmane.org?
On Sat, Feb 28, 2009 at 6:57 AM, ael law_ence@ntlworld.com 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. ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
[Ekiga-list] no incoming calls behing an ADSL modem
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 :) ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] no incoming calls behing an ADSL modem
On Sat, Feb 28, 2009 at 3:49 PM, H. S. hs.sa...@gmail.com 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. ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] PTLIB alsa plugin status
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 ptlibopal 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 ALSASetting buffers, size: 3840, count: 5 13:45:49.402 ALSADevice default Opened 13:45:49.438 ALSASetting 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@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list -- Derek Smithies Ph.D. IndraNet Technologies Ltd. Email: de...@indranet.co.nz ph +64 3 365 6485 Web: http://www.indranet-technologies.com/ ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] PTLIB alsa plugin status
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 ALSASetting buffers, size: 3840, count: 5 13:45:49.402 ALSADevice default Opened 13:45:49.438 ALSASetting 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 ptlibopal. The default values for codec sizes in ptlibopal 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@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list -- Derek Smithies Ph.D. IndraNet Technologies Ltd. Email: de...@indranet.co.nz ph +64 3 365 6485 Web: http://www.indranet-technologies.com/ ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
