Bug 673647

(In reply to comment #0)
> Description of problem:
> I call to the Echo server on sip:500. A female voice should then say
> a few sentences and then you can use it to test. Except, for some reason it
> doesn't do this every time you make a call. In this case, one is connected, but
> the female voice is not there and saying something yourself does not result in
> a response either.

the test server isn't Fedora infrastructure.

> It might be that there is a general audio problem. The Ringing Device is
> Default (PTLIB/ALSA) and the Output device is Default (PTLIB/ALSA). This is
> worrying, because it should use PulseAudio. 

ekiga 3.2 doesn't support PulseAudio but it still uses the alsa support in PA. 3.4 when released will support PA.

> According to http://wiki.ekiga.org/index.php/Audio_setup#Pulse_Audio it seems
> that it basically doesn't work with PulseAudio unless a user jumps through
> hoops.

That's correct for the current stable release.

(In reply to comment #1)
> (In reply to comment #0)
> > Description of problem:
> > I call to the Echo server on sip:500. A female voice should then say
> > a few sentences and then you can use it to test. Except, for some reason it
> > doesn't do this every time you make a call. In this case, one is connected, but
> > the female voice is not there and saying something yourself does not result in
> > a response either.
> 
> the test server isn't Fedora infrastructure.
Uhm, who cares about that? Fedora ships this piece of software, doesn't it? Also, I _highly_ doubt it is only the echo server that doesn't work... 
> 
> > It might be that there is a general audio problem. The Ringing Device is
> > Default (PTLIB/ALSA) and the Output device is Default (PTLIB/ALSA). This is
> > worrying, because it should use PulseAudio. 
> 
> ekiga 3.2 doesn't support PulseAudio but it still uses the alsa support in PA.
> 3.4 when released will support PA.
> 
> > According to http://wiki.ekiga.org/index.php/Audio_setup#Pulse_Audio it seems
> > that it basically doesn't work with PulseAudio unless a user jumps through
> > hoops.
> 
> That's correct for the current stable release.
Ah, so you (as in the Fedora project) released something which doesn't work by default? I am sure that people will say to you that was a smart move.

This bug is a bug. How on Earth you can say it is 'NOTABUG' is beyond me. Ekiga is supposed to be some kind of Skype replacement, except ... it DOES NOT WORK. 

I am not sure what your idea is of a 'bug', but I can tell you that this is one. 

If this is not a bug, then what is? Next thing you are going to say is that when I find a bug in the implementation of some kernel call that it is a Linux kernel problem and not a "Fedora problem".

Please go to Clueville and obtain some clue. 

Why I cannot change the status to "REOPENED" is also beyond me. I suppose you have some special rights which enable you to make these stupid decisions.

First, please be nice. I do this in my own time, unpaid. There is no need to be rude.

> > > I call to the Echo server on sip:500. A female voice should then say
> > > a few sentences and then you can use it to test. Except, for some reason it
> > > doesn't do this every time you make a call. In this case, one is connected, but
> > > the female voice is not there and saying something yourself does not result in
> > > a response either.
> > 
> > the test server isn't Fedora infrastructure.
> Uhm, who cares about that? Fedora ships this piece of software, doesn't it?
> Also, I _highly_ doubt it is only the echo server that doesn't work... 

If the echo server provided by a third party isn't working I can't click my fingers. If your cell tower is down do you call the manufacturer of your cell phone and yell at them?

> > > It might be that there is a general audio problem. The Ringing Device is
> > > Default (PTLIB/ALSA) and the Output device is Default (PTLIB/ALSA). This is
> > > worrying, because it should use PulseAudio. 
> > 
> > ekiga 3.2 doesn't support PulseAudio but it still uses the alsa support in PA.
> > 3.4 when released will support PA.
> > 
> > > According to http://wiki.ekiga.org/index.php/Audio_setup#Pulse_Audio it seems
> > > that it basically doesn't work with PulseAudio unless a user jumps through
> > > hoops.
> > 
> > That's correct for the current stable release.
> Ah, so you (as in the Fedora project) released something which doesn't work by
> default? I am sure that people will say to you that was a smart move.

It works for 1000s of other users.

> This bug is a bug. How on Earth you can say it is 'NOTABUG' is beyond me. Ekiga
> is supposed to be some kind of Skype replacement, except ... it DOES NOT WORK. 

It does for 1000s of other users.

> I am not sure what your idea is of a 'bug', but I can tell you that this is
> one. 

Maybe your not describing your problem well then. 

> If this is not a bug, then what is? Next thing you are going to say is that
> when I find a bug in the implementation of some kernel call that it is a Linux
> kernel problem and not a "Fedora problem".

Well you reported a lot of issues. One was support for PulseAudio. That problem will be fixed in Fedora 15 and may well if at all possible get back ported when its stable. Its far from that yet and we have a solution that works well generally for most people at the moment.

> Please go to Clueville and obtain some clue. 

I have lots of clue. I've been supporting ekiga for about 3 years in Fedora, and have been using it since its initial gnomemeeting release around 10 years ago.
 
> Why I cannot change the status to "REOPENED" is also beyond me. I suppose you
> have some special rights which enable you to make these stupid decisions.

No idea. As the maintainer of the package you are correct I have some special rights. As the bug reporter so do you. I have no idea what the difference is as I don't maintian bugzilla, just ekiga.