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 612460 - Empathy freezes on attempting to place a SIP call
Empathy freezes on attempting to place a SIP call
Status: RESOLVED NOTGNOME
Product: empathy
Classification: Core
Component: VoIP
unspecified
Other Linux
: Normal critical
: ---
Assigned To: empathy-maint
Depends on:
Blocks:
 
 
Reported: 2010-03-10 18:42 UTC by Jeremy Nickurak
Modified: 2011-08-29 10:12 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jeremy Nickurak 2010-03-10 18:42:20 UTC
Whenever I try to place a call with SIP, empathy freezes. Occurs on calls to my local SIP/PSTN provider, and calls to 500@ekiga.net (not behind a NAT in either case), if it matters.

Using telepathy-sofiasip 0.6.1 and empathy 2.29.90 (from the ubuntu telepathy ppa).

Marking critical, since it's a total freeze of empathy.

atrus@yeesha:~$ empathy 
(empathy:27744): tp-fs-DEBUG: GetSessionHandlers replied: 
(empathy:27744): tp-fs-DEBUG:   - session /org/freedesktop/Telepathy/Connection/sofiasip/sip/_31789031191_40did_2evoip_2eles_2enet/MediaChannel0/MediaSession2
(empathy:27744): tp-fs-DEBUG:     type rtp
(empathy:27744): tp-fs-DEBUG: adding session handler /org/freedesktop/Telepathy/Connection/sofiasip/sip/_31789031191_40did_2evoip_2eles_2enet/MediaChannel0/MediaSession2, type rtp
(empathy:27744): tp-fs-DEBUG: calling MediaSessionHandler::Ready
(empathy:27744): tp-fs-DEBUG: New stream, stream_id=0, media_type=0, direction=3
(empathy:27744): tp-fs-DEBUG: stream 0 0x8ed9800 (audio) get_all_properties_cb: Adding STUN server (old API) :3478

(empathy:27744): GLib-GObject-WARNING **: IA__g_object_newv: object class `FsRawUdpStreamTransmitter' has no property named `controlling-mode'
Comment 1 David Laban 2010-03-10 18:55:06 UTC
I can also confirm this bug, and agree that it should be critical because it also affects a client. If you want a test account to reproduce it with, you can use my test account:

username: fargouser@opensips.org
ask me in private for the password
calling echo@iptel.org will make the lock-up happen.

http://pastebin.ca/1822477 

[18:43] <johanbr> atrus, that's apparently a bug in farsight2, according to what I was told yesterday
[18:43] <johanbr> fixed in git, or you can downgrade to telepathy-sofiasip 0.5.19 as a workaround
Comment 2 Guillaume Desmottes 2010-03-15 12:23:17 UTC
Olivier: do you confirm that this one is a fs2 issue? Any chance to have a release soonish?
Comment 3 Olivier Crête 2010-03-18 12:18:29 UTC
I'm not sure this is a known bug in fs2, but it looks like that.. I will investigate.
Comment 4 Omer Akram 2010-03-23 17:39:45 UTC
Also reported at: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/526158
Comment 5 Mikhail Zabaluev 2010-03-24 10:13:11 UTC
This is not reproducible with telepathy-sofiasip 0.6.2.
Most likely the problem has to do with bogus values of legacy channel properties for NAT traversal, which were fixed in this release. But this is bad form to hang like that; IIRC a workaround was made for Maemo, but I thought it was merged into upstream libtelepathy-farsight too.

Meanwhile, try to set the STUN server parameter to something usable, like "stun.ekiga.net".
Comment 6 Mikhail Zabaluev 2010-03-24 10:48:00 UTC
(In reply to comment #5)
> I thought it was merged into upstream libtelepathy-farsight too.

And sure enought it was, but it hasn't been released yet.
Please try with telepathy-farsight built from master branch at:
git://git.collabora.co.uk/git/telepathy-farsight.git
Comment 7 Guillaume Desmottes 2010-03-24 11:00:08 UTC
Thanks Mikhail!