Bug 41782

Summary:	Empathy don't pick up call for SIP account
Product:	Telepathy	Reporter:	José Illescas Pérez <jip>
Component:	rakia	Assignee:	Mikhail Zabaluev <mikhail.zabaluev>
Status:	RESOLVED DUPLICATE	QA Contact:	Telepathy bugs list <telepathy-bugs>
Severity:	normal
Priority:	medium
Version:	0.8
Hardware:	x86-64 (AMD64)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:
Attachments:	Sofiasip log Sofia sip log Mission Control log Sofia sip log Mission Control log Telepathy Sofiasip log Incoming call

Description José Illescas Pérez 2011-10-14 00:35:52 UTC

Hello,

I've a problem with Empathy with SIP. The problem occurs in Empathy 3.2 and also in the previous version of Empathy 3.0.

When I receive a call for my SIP account, it appears the notification in
desktop for pick up or reject.

I click in pick up, but don't pick up. The call is lost.

Ekiga works and Twinkle too.

I'm using Arch Linux with GNOME 3.2. The SIP service is Cisco Unified
Communication Manager 7.1.5.

I attach logs for mission-control and telepathy-sofiasip.

I've opened a bug un bugzilla.gnome.org:

https://bugzilla.gnome.org/show_bug.cgi?id=660768

Best regards.

Comment 1 José Illescas Pérez 2011-10-14 00:36:28 UTC

Created attachment 52317 [details]
Sofiasip log

Comment 2 José Illescas Pérez 2011-10-14 00:37:17 UTC

The version of telepathy-sofiasip is 0.7.1

Comment 3 Mikhail Zabaluev 2011-10-14 00:51:24 UTC

Looks like you have no audio codecs available:

tpsip/media-channel-WARNING: 13/10/11 09:06:59.403124: priv_session_respond: cannot respond with a valid SDP answer, were all streams closed?

Is there anything about audio codecs in Empathy logs from Farsight?

Comment 4 Mikhail Zabaluev 2011-10-14 00:57:45 UTC

(In reply to comment #3)
> Looks like you have no audio codecs available:

Scratch that. It basically bails out after receiving an invite and accepting the call, with no media negotiation even logged.

Can I look at the SIP traffic in a packet capture, or can you run telepathy-sofiasip with environment variable TPORT_LOG=1? You'll also need TPSIP_PERSIST=1 if you run it manually from a user shell.

Comment 5 José Illescas Pérez 2011-10-14 03:11:11 UTC

Created attachment 52323 [details]
Sofia sip log

I attach sofia sip log in incoming call with environment variables:

TPORT_LOG=1
TPSIP_PERSIST=1

Best regards.

Comment 6 José Illescas Pérez 2011-10-14 03:11:46 UTC

Created attachment 52324 [details]
Mission Control log

I attach mission control log.

Comment 7 Mikhail Zabaluev 2011-10-14 03:27:02 UTC

(In reply to comment #5)
> Created an attachment (id=52323) [details]
> Sofia sip log
> 
> I attach sofia sip log in incoming call with environment variables:
> 
> TPORT_LOG=1
> TPSIP_PERSIST=1

Somehow there is no effect. Can you make sure that the variables are exported and telepathy-sofiasip runs in the shell that exports them?
Also export TPSIP_DEBUG=all for good measure, though I think it should not matter for Telepathy logging.

Comment 8 José Illescas Pérez 2011-10-14 03:52:48 UTC

Created attachment 52325 [details]
Sofia sip log

I execute empathy as well:

$ export TPORT_LOG=1
$ export TPSIP_PERSIST=1
$ export TPSIP_DEBUG=all
$ empathy

I attach sofia sip log.

Regards.

Comment 9 José Illescas Pérez 2011-10-14 03:53:14 UTC

Created attachment 52326 [details]
Mission Control log

I attach mission control log.

Comment 10 Mikhail Zabaluev 2011-10-14 03:57:36 UTC

(In reply to comment #8)
> I execute empathy as well:

No, empathy runs in a different process.
You can run telepathy-sofiasip in the shell with those environment variables and control it from empathy as it is normally launched on the desktop.

Comment 11 José Illescas Pérez 2011-10-14 04:07:19 UTC

Created attachment 52327 [details]
Telepathy Sofiasip log

Ups!, ok. I think that is the correct log. I attach. Regards.

Comment 12 José Illescas Pérez 2011-10-14 04:13:34 UTC

Created attachment 52328 [details]
Incoming call

When I receive incoming call and click in accept call, empathy open a new window for do outgoing call. This is rare. I attach window. Regards.

Comment 13 Mikhail Zabaluev 2011-10-14 05:42:07 UTC

(In reply to comment #11)
> Created an attachment (id=52327) [details]
> Telepathy Sofiasip log
> 
> Ups!, ok. I think that is the correct log. I attach. Regards.

Thank you, now it's clear.
The server wants us to accept the call in a 3rd party call control scenario, which we don't currently support. Bug #32808 already exists for the issue.

*** This bug has been marked as a duplicate of bug 32808 ***

Comment 14 José Illescas Pérez 2011-10-14 07:07:54 UTC

(In reply to comment #13)
> (In reply to comment #11)
> > Created an attachment (id=52327) [details] [details]
> > Telepathy Sofiasip log
> > 
> > Ups!, ok. I think that is the correct log. I attach. Regards.
> 
> Thank you, now it's clear.
> The server wants us to accept the call in a 3rd party call control scenario,
> which we don't currently support. Bug #32808 already exists for the issue.
> 
> *** This bug has been marked as a duplicate of bug 32808 ***

Is it normal for Ekiga and Twinkle work properly?.

Regards.

Comment 15 Mikhail Zabaluev 2011-10-14 07:27:05 UTC

(In reply to comment #14)
> Is it normal for Ekiga and Twinkle work properly?.

Yes, they have that feature and we don't.

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.