Bug 30362

Summary: Keepalive OPTION requests fail when the SIP providers proxy requires authentication
Product: Telepathy Reporter: Tschaka <stuff4tschaka>
Component: rakiaAssignee: Mikhail Zabaluev <mikhail.zabaluev>
Status: RESOLVED MOVED QA Contact: Telepathy bugs list <telepathy-bugs>
Severity: critical    
Priority: medium Keywords: NEEDINFO
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description Tschaka 2010-09-24 06:24:35 UTC
telepathy-sofiasip is version 0.6.3-1~ppa10.04+1. The same behaviour (although
not debugged) happens with version 0.6.2-devel on the N900

libsofia-sip-ua0 is version 1.12.10-4

The OPTION keepalive packages sent by telepathy are not correctly recognized by e.g. sipgate.de's proxy server, when the server requires proxy authentication. Telepathy so far does not seem to offer proxy authentication and those keep alive packages are getting refused with a 407 error. 

Without keep alive packages, the connection sooner or later is considered as closed from the server side.
Comment 1 Mikhail Zabaluev 2010-12-30 05:32:46 UTC
Strange, I can see the code in sofia-sip that should restart the OPTIONS request with authentication on a 407 error code.

I don't have an account at sipgate.de and I have trouble registering at the German-language website :)
Can you collect debug logs (the "sofiasip" log view in Empathy) while running telepathy-sofiasip with TPSIP_PERSIST=1 NUA_DEBUG=5 TPORT_LOG=1 in its environment and connected to sipgate.de?
Comment 2 GitLab Migration User 2019-12-03 19:36:57 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/12.

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.