Bug 24260 - Cannot establish SIP call.
Summary: Cannot establish SIP call.
Status: RESOLVED NOTOURBUG
Alias: None
Product: Telepathy
Classification: Unclassified
Component: rakia (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Mikhail Zabaluev
QA Contact: Telepathy bugs list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-01 11:24 UTC by Philipp Weis
Modified: 2009-10-28 15:16 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments
empathy.log (20.21 KB, application/octet-stream)
2009-10-01 11:24 UTC, Philipp Weis
Details
sogiasip.log (21.23 KB, application/octet-stream)
2009-10-01 11:24 UTC, Philipp Weis
Details
New Empathy Log (20.43 KB, application/octet-stream)
2009-10-28 10:16 UTC, Philipp Weis
Details
New Sofiasip Log (2.08 KB, text/plain)
2009-10-28 10:16 UTC, Philipp Weis
Details
coded-preferences (380 bytes, application/octet-stream)
2009-10-28 10:16 UTC, Philipp Weis
Details

Description Philipp Weis 2009-10-01 11:24:14 UTC
Created attachment 29981 [details]
empathy.log

I set up one of my SIP account in empathy and can receive calls, but I'm unable
to place any calls. Ekiga works just fine with the same account.

When I call an SIP contact, a connection window opens and it says
"Connecting..." in the status bar for about a minute, and then "Disconnected".

I attached debug logs from both empathy and telepathy-sofiasip, with my phone
number masked out.

I originally reported this as https://bugzilla.gnome.org/show_bug.cgi?id=596887 but was asked to report it again here.
Comment 1 Philipp Weis 2009-10-01 11:24:36 UTC
Created attachment 29982 [details]
sogiasip.log
Comment 2 Mikhail Zabaluev 2009-10-20 04:37:00 UTC
The proxy responds with 480 request timeout. Probably the VoIP gateway becomes terminally confused with your SDP offer. Which, among other interesting things, contains two DTMF payloads with different bitrates. I'll file a Farsight bug about this.
Comment 3 Mikhail Zabaluev 2009-10-20 04:49:50 UTC
As a possible workaround, try to switch off the funky 16 bit codecs such as SPEEX and SIREN.
Comment 4 Mikhail Zabaluev 2009-10-20 07:09:26 UTC
(In reply to comment #3)
> As a possible workaround, try to switch off the funky 16 bit codecs such as
> SPEEX and SIREN.

I mean the 16kbps codecs, of course.
Comment 5 Philipp Weis 2009-10-20 21:46:46 UTC
Thanks for looking into this. I just disabled SPEEX and SIREN by editing the non-configuration file /usr/share/empathy/codec-preferences. It doesn't change anything. The codecs now appear as follows in the debug log, but everything else remains the same.

(empathy:15241): tp-fs-DEBUG: New stream, stream_id=0, media_type=0, direction=2
(empathy:15241): tp-fs-DEBUG: stream 0 0x191e180 (audio) get_all_properties_cb: Adding STUN server (old API) 217.10.79.2:10000
(empathy:15241): tp-fs-DEBUG: stream 0 0x191e180 (audio) _tf_stream_try_sending_codecs: called (send_local:1 send_supported:0)
(empathy:15241): tp-fs-DEBUG: stream 0 0x191e180 (audio) _tf_stream_try_sending_codecs: 0: audio PCMU clock:8000 channels:0
(empathy:15241): tp-fs-DEBUG: stream 0 0x191e180 (audio) _tf_stream_try_sending_codecs: 8: audio PCMA clock:8000 channels:0
(empathy:15241): tp-fs-DEBUG: stream 0 0x191e180 (audio) _tf_stream_try_sending_codecs: 3: audio GSM clock:8000 channels:0
(empathy:15241): tp-fs-DEBUG: stream 0 0x191e180 (audio) _tf_stream_try_sending_codecs: 99: audio telephone-event clock:8000 channels:0 events=0-15
(empathy:15241): tp-fs-DEBUG: stream 0 0x191e180 (audio) fs_codecs_to_tp: adding codec PCMU [0]
(empathy:15241): tp-fs-DEBUG: stream 0 0x191e180 (audio) fs_codecs_to_tp: adding codec PCMA [8]
(empathy:15241): tp-fs-DEBUG: stream 0 0x191e180 (audio) fs_codecs_to_tp: adding codec GSM [3]
(empathy:15241): tp-fs-DEBUG: stream 0 0x191e180 (audio) fs_codecs_to_tp: adding codec telephone-event [99]
(empathy:15241): tp-fs-DEBUG: stream 0 0x191e180 (audio) _tf_stream_try_sending_codecs: calling MediaStreamHandler::Ready
Comment 6 Jeremy Nickurak 2009-10-22 08:02:25 UTC
So, if this is listed as 'notourbug', whose bug is it?
Comment 7 Mikhail Zabaluev 2009-10-27 04:49:30 UTC
(In reply to comment #6)
> So, if this is listed as 'notourbug', whose bug is it?

The gateway's, or the proxy's, if my assumption is right.
It should ignore the payloads in SDP it does not support.
Comment 8 Mikhail Zabaluev 2009-10-27 04:51:16 UTC
(In reply to comment #5)
> Thanks for looking into this. I just disabled SPEEX and SIREN by editing the
> non-configuration file /usr/share/empathy/codec-preferences. It doesn't change
> anything. The codecs now appear as follows in the debug log, but everything
> else remains the same.

Try also disabling the GSM codec.
It might be also the telephone-event payload (DTMF) that's causing trouble, I don't remember how to disable it.
Comment 9 Philipp Weis 2009-10-28 10:15:20 UTC
Alright, I disabled both telephone-event and GSM, and I still can't connect. Attached are my latest logs from empathy and telepathy-sofiasip, and my codec-preferences file. This is also with the latest packages from debian unstable, i.e. empathy 2.28.1.1-1 and telepathy-sofiasip 0.5.18-1.
Comment 10 Philipp Weis 2009-10-28 10:16:15 UTC
Created attachment 30776 [details]
New Empathy Log
Comment 11 Philipp Weis 2009-10-28 10:16:33 UTC
Created attachment 30777 [details]
New Sofiasip Log
Comment 12 Philipp Weis 2009-10-28 10:16:59 UTC
Created attachment 30778 [details]
coded-preferences
Comment 13 Olivier Crête 2009-10-28 10:28:20 UTC
To get a useful log from tp-ssip, you need to set TPORT_LOG=1
Also, when you attach files, please set the right mime-type (in this case, text/plain)
Comment 14 Philipp Weis 2009-10-28 15:16:06 UTC
Thanks for mentioning the tport debug option. Looking at these logs, I see a "407 Proxy Authentication Failed" message. I'm investigating with my sip provider to figure out what's going on.

Wouldn't it be nice if empathy would pass this error on to the user?


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.