Please see bug 9254 comment 9 onwards Ekiga shows udp error messages when calling the echo service, after listening to the recorded message and also the callback service fails to answer. Ports forwarded as per http://wiki.ekiga.org/index.php/Enable_port_forwarding_manually and firewall disabled. Reproducible: Steps to Reproduce:
CC: (none) => alien, junk_no_spam, luigiwalser
imho this might be a configuration issue... by design this isn't the easiest package. and it might be related to the environment in which it's tested. who knows, perhaps someone else has an easier time setting this stuff up. or, it could be that something is broken... btw: the callback service did work for me. it called me back. i just heard no audio.
Yes the callback did call back but I was unable to answer it. The popup asked to answer it and clicking to do so made the popup disappear but it was obviously unable to establish the connection as in a minute or two it said the call was missed. Also the connection stats at the bootom of the window on echo service which seem to indicate audio/video, the audio goes from 8.0/8.0 to 8.0/0.0 when the recorded message has finished playing. I don't see any configuration options for UDP.
(In reply to claire robinson from comment #2) > I don't see any configuration options for UDP. Have you installed the wget, netcat-openbsd, bind-utils rpms and executed the port test script https://bugs.mageia.org/attachment.cgi?id=3853? If you run pavucontrol, boost the mic output and can hear you thumping the mic you know the mic and sound system devices are working. If the port test passes you know there are no problems with ekiga being able to use the ports. If click the Play button in ekiga->Edit->General->Sound Events and hear sounds you know you should be able to hear anything. What is left is the ekiga->Edit->Audio->Devices Output Device: mic selection. In the past I think you had to exit ekiga after device changes for them to take effect. Not sure about that on 4.0.1.0 If you still have problems then I would guess it is the software on a 32 bit install. :( I completed a clean install updates on mga2 64 bit and 4.0.1 works.
Keywords: (none) => NEEDINFOCC: (none) => stormi
CC: (none) => fundawang, nicolas.lecureuil
This message is a reminder that Mageia 2 is nearing its end of life. Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- The Mageia Bugsquad
Closing this now due to Mageia 2 EOL. http://blog.mageia.org/en/2013/11/21/farewell-mageia-2/
Status: NEW => RESOLVEDResolution: (none) => OLD