[Jaunty] Ekiga occupies >82% of a Centrino computer's CPU time

[Detlef Lechner]

Binary package hint: ekiga

uname -a; Linux MD97600 2.6.28-13-generic #45-Ubuntu SMP Tue Jun 30 19:49:51 UTC 2009 i686 GNU/Linux

I notice that today I cannot obtain an echo from <email address hidden>. But I could so in the past. I cannot remember that I changed anything in my computer's configuration of relevance to Ekiga. But I cannot rule out that in the time between there was a dist-update.

The output of '~ekiga -d 4 2>output1.txt is http://paste.ubuntuusers.de/395718/

Let me know what additional test data do you need from me.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/ekiga
Package: ekiga 3.2.0-0ubuntu2
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
SourcePackage: ekiga
Uname: Linux 2.6.28-13-generic i686

[Yannick Defais (sevmek)]

Hi,

Detlef and I had an IRC session about this issue.

The issue is the following:
the router Detlef use is a FRITZ!Box Fon. In his setup some ports in the UDP range Ekiga use (5060 to 5100) for the media session (RTP) were open and some were closed for inbound connection. As a result, sometimes there was sound when calling the echo test and sometimes (most of time) there was no sound. Ekiga pick up somewhat randomly the port in the above range.

The pratical solution was to open some ports in the router; he opened ports 5061 to 5065 in UDP, and to configure Ekiga to use those ports only:
Open a terminal and start "gconf-editor", then find the key "/apps/ekiga/protocols/ports/udp_port_range", change it from "5060:5100" to "5061:5065", restart ekiga.

After that, the call to the echo test (<email address hidden>) works.

Best regards,
Yannick

[Yannick Defais (sevmek)]

Nedd info: Is the 82% CPU issue still valid now?

[Detlef Lechner (detlef-lechner)]

The 82% CPU load still appears.

[Yannick Defais (sevmek)]

Hi,

Ubuntu Karmic comes with Ekiga 3.2.5 which has numerous fixes. Could you give it a try?

Best regards,
Yannick

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.