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 757883 - No outbound voice when making calls
No outbound voice when making calls
Status: RESOLVED OBSOLETE
Product: empathy
Classification: Core
Component: VoIP
3.12.x
Other Linux
: Normal major
: ---
Assigned To: empathy-maint
Depends on:
Blocks:
 
 
Reported: 2015-11-10 13:47 UTC by cpw+bugs
Modified: 2018-05-22 19:06 UTC
See Also:
GNOME target: ---
GNOME version: 3.17/3.18


Attachments
debug log (3.02 MB, application/x-xz)
2016-01-28 20:04 UTC, Michael Catanzaro
Details

Description cpw+bugs 2015-11-10 13:47:42 UTC
Version data: Empathy 3.12.11. Gstreamer 1.6.1. Pulseaudio 7.0.2.

There is no outbound voice (from computer to telephony system) when making or receiving calls.

Other clients work successfully for the same parameters, which tends to rule out other causes of error.

The problem seems to have come about with an upgrade to gstreamer 1.6 from 1.4.5. I tried (and failed) to rollback to 1.4.5 to test this hypothesis. Gstreamer is a very difficult product to rollback, sadly.

Dist: Debian. Reported the same issue at debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801904 but it hasn't been looked at as far as I can tell.

Happy to try anything to diagnose the issue. I've tried debugging the gstreamer pipeline, but it seems to be very challenging to figure out where the outbound voice is getting lost, with the debugging to hand.

Looking at the network traces to my SIP server, it seems clear that I'm sending only silence RTP packets from my computer to my SIP server, so I think that the voice is getting lost in the pipeline. I've tried to make simple pipelines, and they all seem to work.
Comment 1 Michael Catanzaro 2016-01-28 18:19:51 UTC
CCing GStreamer developers
Comment 2 Tim-Philipp Müller 2016-01-28 18:45:00 UTC
You have excluded the possibility of an Empathy or pulseaudio upgrade being the culprit?

You could try to run empathy like this from a terminal window:

 $ GST_DEBUG=*:6 empathy 2>dbg.log

and capture a few seconds of making a call. Maybe there's something obvious in the log to see what's happening.

To be sure, you have checked your microphone volume control and the pulseaudio settings and made sure that the input device is set up properly? (In pavolume under 'Input devices' you should see the Microphone and a line level if you make some noise)
Comment 3 Tim-Philipp Müller 2016-01-28 18:45:24 UTC
the log will be large, compress with xz -9.
Comment 4 Olivier Crête 2016-01-28 19:42:57 UTC
Actually, you need to run /usr/libexec/empathy-call, not empathy itself to get a log of the GStreamer part.
Can you run it as:
EMPATYHY_DEBUG=all GST_DEBUG=*:6 /usr/libexec/empathy-call 2>dbg.log
Comment 5 Michael Catanzaro 2016-01-28 20:04:07 UTC
Created attachment 319969 [details]
debug log

Thanks for responding. Debug log attached.

(In reply to Tim-Philipp Müller from comment #2)
> You have excluded the possibility of an Empathy or pulseaudio upgrade being
> the culprit?

It's certainly not due to any change in Empathy or Telepathy or sofiasip, which is clear from a quick check of the changelog. GStreamer, being the healthy changing project, does seem like the most likely culprit. And the issue is relatively recent, from around the time GStreamer 1.6 started to hit distros. I never experienced this bug in Fedora 22 (GStreamer 1.4), but it always occurs in Fedora 23 (GStreamer 1.6).

> To be sure, you have checked your microphone volume control and the
> pulseaudio settings and made sure that the input device is set up properly?
> (In pavolume under 'Input devices' you should see the Microphone and a line
> level if you make some noise)

I see the sound level change with my voice in gnome-control-center, and I can speak with this microphone using various $PROPRIETARY_SERVICES.
Comment 6 Michael Catanzaro 2016-01-28 20:12:49 UTC
(In reply to Michael Catanzaro from comment #5)
> And the
> issue is relatively recent, from around the time GStreamer 1.6 started to
> hit distros. I never experienced this bug in Fedora 22 (GStreamer 1.4), but
> it always occurs in Fedora 23 (GStreamer 1.6).

There was also a major PulseAudio upgrade between F22 and F23, though.
Comment 7 Xabier Rodríguez Calvar 2016-01-29 10:56:37 UTC
I confirm that I have this issue and I have been having it in my Debian testing for at least a couple of months already.

Sorry that it took so long, but for some reason empathy left only my Google online account and wiped out the rest.
Comment 8 Michael Catanzaro 2016-05-12 16:31:35 UTC
It's fixed for me in Fedora 24, I suspect due to the GStreamer 1.8 upgrade. Is anyone still experiencing this with GStreamer 1.8?
Comment 9 GNOME Infrastructure Team 2018-05-22 19:06:35 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME'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.gnome.org/GNOME/empathy/issues/854.