Bug 30356

Summary:	No keep alive packets are sent when the method is set to Automatic or REGISTER
Product:	Telepathy	Reporter:	Tschaka <stuff4tschaka>
Component:	rakia	Assignee:	Mikhail Zabaluev <mikhail.zabaluev>
Status:	RESOLVED MOVED	QA Contact:	Telepathy bugs list <telepathy-bugs>
Severity:	normal
Priority:	low	Keywords:	NEEDINFO
Version:	unspecified
Hardware:	All
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description Tschaka 2010-09-24 02:50:00 UTC

telepathy-sofiasip is version 0.6.3-1~ppa10.04+1. The same behaviour (although not debugged happens to version 0.6.2-devel on the N900)

libsofia-sip-ua0 is version 1.12.10-4

When the keep alive method is set to REGISTER or Automatic (which probably implies REGISTER), there are no keep alive packages being sent (nothing is being detected by wireshark or the empathy-debugger), which means the connection gets closed from the server side after a certain amount of time. For sipgate.de this happens after 600 seconds.

Empathy and the N900 Account manager keep on stating, that the connection is still alive, while e.g. the sipgate.de web interface lists you as offline. Hence, when you are getting called, the call does not get through as you are offline. 

With the OPTIONS method it seems to work. However there is another problem with missing proxy authentication where proxies are present, which let's the keep alive requests being unsuccessful (filed in a separate bug).

Comment 1 Mikhail Zabaluev 2010-09-24 04:27:26 UTC

(In reply to comment #0)
> When the keep alive method is set to REGISTER or Automatic (which probably
> implies REGISTER),

Actually, automatic should imply OPTIONS.

With REGISTER, as we have discovered, the proxy overrides the expiration time to 600 seconds and the UA stack is obliged to follow, so REGISTER is not good as a keepalive method in this case.

> With the OPTIONS method it seems to work. However there is another problem with
> missing proxy authentication where proxies are present, which let's the keep
> alive requests being unsuccessful (filed in a separate bug).

They are unsuccessful from the server side, but the interval is followed on the client side. I should think about authenticating OPTIONS; at least it should not break anything. With the keepalive usage, there's a clear benefit in keeping the OPTIONS request small, so it does not include the authentication token obtained by REGISTER. Maybe the stack should learn to keep it after the first such error status.

Comment 2 Mikhail Zabaluev 2010-11-03 08:38:16 UTC

(In reply to comment #1)
> Actually, automatic should imply OPTIONS.

Can you still reproduce the issue when the method is set to automatic?

Comment 3 GitLab Migration User 2019-12-03 19:36:55 UTC

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-rakia/issues/11.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.