After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 685097 - Ekiga missed calls
Ekiga missed calls
Status: RESOLVED FIXED
Product: ekiga
Classification: Applications
Component: Call stack
3.9.x
Other Linux
: Normal major
: ---
Assigned To: Ekiga maintainers
Ekiga maintainers
Depends on:
Blocks:
 
 
Reported: 2012-09-29 13:05 UTC by Stefan Schulze Frielinghaus
Modified: 2013-01-11 08:38 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Logfile -d 3 (76.38 KB, text/plain)
2012-10-21 11:44 UTC, Stefan Schulze Frielinghaus
Details
Logfile -d 4 (203.56 KB, text/plain)
2012-12-22 16:24 UTC, Stefan Schulze Frielinghaus
Details
Logfile -d 3 WORKS (54.59 KB, text/plain)
2012-12-22 16:34 UTC, Stefan Schulze Frielinghaus
Details
Logfile -d 3 and ekiga version 4.0.0 (85.64 KB, text/plain)
2013-01-09 20:59 UTC, Stefan Schulze Frielinghaus
Details
Logfile -d 4 and ekiga version 4.0.0 (206.27 KB, text/plain)
2013-01-09 21:00 UTC, Stefan Schulze Frielinghaus
Details

Description Stefan Schulze Frielinghaus 2012-09-29 13:05:45 UTC
Since version 3.9.90 Ekiga does not respond to a call in a reasonable way anymore. A ring tone is played exactly one time, then a message pops up in the Gnome shell telling me that I should decide if I want to accept the call or not and in the next few milli seconds a new message pops up that I missed the call. That means, I do not have the chance to actually accept the call at all because the second message pops up right after the first one.

I'm using GNOME3 (Fedora 17) and a SIP account (sipgate.de).

The following versions worked fine for me:
ekiga-3.3.2
opal-3.10.2
ptlib-2.10.2

If you need anything else, just let me know.
Comment 1 Damien Sandras 2012-09-30 15:19:42 UTC
I wonder if it could be a bug in libnotify, because I'm not doing anything fancy with the libs.

However, I experienced a similar bug under gnome fallback and found a fix this WE.

Could you try to see if it fixes your problem ?

I would guess it does not, but who knows...
Comment 2 Eugen Dedu 2012-10-02 21:46:48 UTC
What is the value of Timeout... in Preferences->General->CallOptions ?
Comment 3 Stefan Schulze Frielinghaus 2012-10-03 16:51:15 UTC
(In reply to comment #1)
[...]
> Could you try to see if it fixes your problem ?

Uhm what exactly should I try?

(In reply to comment #2)
> What is the value of Timeout... in Preferences->General->CallOptions ?

The timeout is set to 45 seconds.
Comment 4 Eugen Dedu 2012-10-03 17:47:33 UTC
Stefan, send us a -d 4 log.  Maybe there is some packet received which triggers that...
Comment 5 Eugen Dedu 2012-10-16 14:08:12 UTC
Could you send us a -d 4 log?
Comment 6 Stefan Schulze Frielinghaus 2012-10-16 15:39:55 UTC
Sorry for the long delay.

I did some tests and here are the results:

Starting "ekiga -d {1,2,3}" results always in the problem as described above. However, starting "ekiga -d 4" works fine for me, i.e. I can answer incoming calls. This sounds like a race condition to me which does not happen in debugging level 4.

I'm not happy with uploading a debug logfile because it contains hundreds of confidential data, like my phone book. If you really need it in order to solve the problem, I will hopefully find the time to manually check 2300 lines of the log file in order to obfuscate all addresses, IPs and account names.
Comment 7 Eugen Dedu 2012-10-16 16:44:42 UTC
Ok.  I see two problems in your case.  The first is that the notification disappears very fast, and that it shows Missed call.

Are both of them solved with -d 4 ?  With the others -d do both problems appear?
Comment 8 Stefan Schulze Frielinghaus 2012-10-16 20:06:38 UTC
Yes that is right. While starting ekiga in normal mode or in debug mode with levels between 1 and 3, the notification disappears right away and it shows a missed call message.

While in debug mode with level 4 both problems go away, i.e. I can answer a call as I would expect.
Comment 9 Eugen Dedu 2012-10-21 10:47:26 UTC
Stefan, please give us a -d 3 log, where the bug appears...
Comment 10 Stefan Schulze Frielinghaus 2012-10-21 11:44:11 UTC
Created attachment 226920 [details]
Logfile -d 3
Comment 11 Eugen Dedu 2012-12-11 17:44:02 UTC
The problem is that you receive two INVITEs at 3ms interval:

2012/10/21 13:05:34.735	  0:32.385	Opal Liste...c8e355c700	SIP	PDU INVITE sip:1234567@123.456.789.123:5060 received: rem=udp$217.10.79.9:5060,local=udp$123.456.789.123:5060,if=192.168.178.20%wlan0

and

2012/10/21 13:05:34.738	  0:32.388	Opal Liste...c8e355c700	SIP	PDU INVITE sip:1234567@192.168.178.20:5060 received: rem=udp$217.10.79.9:5060,local=udp$123.456.789.123:5060,if=192.168.178.20%wlan0

The second call arrives before the first one gets processed.

I suppose that when using -d 4, the interval is a bit greater, hence giving enough time to the first call to be processed before the second call arrival.

I take care of this bug.
Comment 12 Eugen Dedu 2012-12-14 08:29:34 UTC
Stefan, please give a -d 4 log too, where it works.  If you do not mind, a -d 3 also, where it works, would perhaps be useful too.
Comment 13 Eugen Dedu 2012-12-22 14:17:09 UTC
Any chance to have the -d 4 log?  We need it to understand why there are two INVITEs...
Comment 14 Stefan Schulze Frielinghaus 2012-12-22 16:24:35 UTC
Created attachment 232119 [details]
Logfile -d 4
Comment 15 Stefan Schulze Frielinghaus 2012-12-22 16:34:21 UTC
Created attachment 232120 [details]
Logfile -d 3 WORKS

Ekiga version 3.3.2
Comment 16 Eugen Dedu 2013-01-02 20:31:39 UTC
Stefan, sorry but we need the debug output for ekiga 4.0.0 (for -d 3 and for -d 4), do you mind attaching them?
Comment 17 Stefan Schulze Frielinghaus 2013-01-09 20:59:59 UTC
Created attachment 233105 [details]
Logfile -d 3 and ekiga version 4.0.0
Comment 18 Stefan Schulze Frielinghaus 2013-01-09 21:00:34 UTC
Created attachment 233106 [details]
Logfile -d 4 and ekiga version 4.0.0
Comment 19 Eugen Dedu 2013-01-11 08:38:02 UTC
Fixed with http://opalvoip.svn.sourceforge.net/viewvc/opalvoip?view=revision&revision=28848, thanks for your bug report!  It will appear in 4.0.1, to be released soon.