registry team mailing list archive

[Bug Watch Updater <409103@xxxxxxxxxxxxxxxxxx>]

Launchpad has imported 15 comments from the remote bug at
http://bugs.freedesktop.org/show_bug.cgi?id=24260.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2009-10-01T11:24:14+00:00 Philipp Weis wrote:

Created an attachment (id=29981)
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.

Reply at: https://bugs.launchpad.net/telepathy-
sofiasip/+bug/409103/comments/8

------------------------------------------------------------------------
On 2009-10-01T11:24:36+00:00 Philipp Weis wrote:

Created an attachment (id=29982)
sogiasip.log

Reply at: https://bugs.launchpad.net/telepathy-
sofiasip/+bug/409103/comments/9

------------------------------------------------------------------------
On 2009-10-20T04:37:00+00:00 Mikhail-zabaluev wrote:

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.

Reply at: https://bugs.launchpad.net/telepathy-
sofiasip/+bug/409103/comments/10

------------------------------------------------------------------------
On 2009-10-20T04:49:50+00:00 Mikhail-zabaluev wrote:

As a possible workaround, try to switch off the funky 16 bit codecs such
as SPEEX and SIREN.

Reply at: https://bugs.launchpad.net/telepathy-
sofiasip/+bug/409103/comments/11

------------------------------------------------------------------------
On 2009-10-20T07:09:26+00:00 Mikhail-zabaluev wrote:

(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.

Reply at: https://bugs.launchpad.net/telepathy-
sofiasip/+bug/409103/comments/12

------------------------------------------------------------------------
On 2009-10-20T21:46:46+00:00 Philipp Weis wrote:

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

Reply at: https://bugs.launchpad.net/telepathy-
sofiasip/+bug/409103/comments/13

------------------------------------------------------------------------
On 2009-10-22T08:02:25+00:00 Freedesktop-bugs wrote:

So, if this is listed as 'notourbug', whose bug is it?

Reply at: https://bugs.launchpad.net/telepathy-
sofiasip/+bug/409103/comments/14

------------------------------------------------------------------------
On 2009-10-27T04:49:30+00:00 Mikhail-zabaluev wrote:

(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.

Reply at: https://bugs.launchpad.net/telepathy-
sofiasip/+bug/409103/comments/15

------------------------------------------------------------------------
On 2009-10-27T04:51:16+00:00 Mikhail-zabaluev wrote:

(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.

Reply at: https://bugs.launchpad.net/telepathy-
sofiasip/+bug/409103/comments/16

------------------------------------------------------------------------
On 2009-10-28T10:15:20+00:00 Philipp Weis wrote:

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.

Reply at: https://bugs.launchpad.net/telepathy-
sofiasip/+bug/409103/comments/17

------------------------------------------------------------------------
On 2009-10-28T10:16:15+00:00 Philipp Weis wrote:

Created an attachment (id=30776)
New Empathy Log

Reply at: https://bugs.launchpad.net/telepathy-
sofiasip/+bug/409103/comments/18

------------------------------------------------------------------------
On 2009-10-28T10:16:33+00:00 Philipp Weis wrote:

Created an attachment (id=30777)
New Sofiasip Log

Reply at: https://bugs.launchpad.net/telepathy-
sofiasip/+bug/409103/comments/19

------------------------------------------------------------------------
On 2009-10-28T10:16:59+00:00 Philipp Weis wrote:

Created an attachment (id=30778)
coded-preferences

Reply at: https://bugs.launchpad.net/telepathy-
sofiasip/+bug/409103/comments/20

------------------------------------------------------------------------
On 2009-10-28T10:28:20+00:00 tester@xxxxxxxxx wrote:

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)

Reply at: https://bugs.launchpad.net/telepathy-
sofiasip/+bug/409103/comments/21

------------------------------------------------------------------------
On 2009-10-28T15:16:06+00:00 Philipp Weis wrote:

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?

Reply at: https://bugs.launchpad.net/telepathy-
sofiasip/+bug/409103/comments/22


** Changed in: telepathy-sofiasip
       Status: Unknown => Won't Fix

** Changed in: telepathy-sofiasip
   Importance: Unknown => Medium

** Bug watch added: GNOME Bug Tracker #596887
   https://bugzilla.gnome.org/show_bug.cgi?id=596887

-- 
SIP calls no longer work (Incompatibility with telepathy-sofiasip)
https://bugs.launchpad.net/bugs/409103
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for Debian.