Bug 37269 - XMPP/Jingle doesn't connect while using multiple networks on eth0
Summary: XMPP/Jingle doesn't connect while using multiple networks on eth0
Status: RESOLVED MOVED
Alias: None
Product: nice
Classification: Unclassified
Component: General (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Olivier Crête
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-16 13:05 UTC by butrus.butrus
Modified: 2015-06-26 13:44 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
Log (32.90 KB, text/plain)
2011-05-16 13:05 UTC, butrus.butrus
Details

Note You need to log in before you can comment on or make changes to this bug.
Description butrus.butrus 2011-05-16 13:05:11 UTC
Created attachment 46783 [details]
Log

I experienced a strange behaviour of the Emapthy/Telepathy when trying to make an audio call over XMPP/Jingle. (More precisely, the call is initiated by the other part which is using the Psi XMPP client.) This worked fine until I configured my Laptop to have more networks hung on the eth0 interfaces (I used NetworkManager as provided by up-to-date Fedora 14: I Simply added in nm-applet > right-click-menu > Edit connections > Wired > [some connection] > IPv4 Settings > Adresses more IP / mask entries).

The reason for this setup was that I configured in this time some routers and similar devices which have they default adresses set-up mostly in the 192.168.0.0/24, 192.168.1.0/24 or 192.168.2.0/24 address space. The aim of setting up more addresses was not to have to switch between various NM profiles while configuring the routers etc.

Now with this setup the above mentioned call cannot be set up (It says something like "the connection cannot be established").

See attached ANONYMIZED log (Empathy -> Help -> Debug -> Empathy.AudioVideo). (192.168.*MY*.*IP* is the address seen from my LAN gateway)

I'm currently using the up-to-date telepathy/empathy packages from Fedora 14:

$ rpm -qa | grep pathy
telepathy-glib-0.11.16-1.fc14.i686
gnome-phone-manager-telepathy-0.65-9.fc14.i686
telepathy-haze-0.4.0-2.fc14.i686
telepathy-gabble-0.10.5-1.fc14.i686
telepathy-filesystem-0.0.2-1.fc12.noarch
telepathy-logger-0.1.7-1.fc14.i686
python-telepathy-0.15.18-1.fc14.noarch
empathy-2.32.2-1.fc14.i686
telepathy-idle-0.1.7-1.fc14.i686
telepathy-farsight-0.0.14-2.fc14.i686
telepathy-stream-engine-0.5.11-1.fc12.i686
telepathy-sofiasip-0.6.6-1.fc14.i686
telepathy-mission-control-5.6.1-1.fc14.i686
telepathy-butterfly-0.5.14-1.fc14.noarch
telepathy-salut-0.4.0-1.fc14.i686
Comment 1 Olivier Crête 2011-05-16 13:17:23 UTC
hard to say, my bet would be a bug in Psi.

In a shell, run :
EMPATHY_PERSIST=1 NICE_DEBUG=all /usr/libexec/empathy-av >log

and attach the log, that may give a further hint.. but it really sounds like a Psi bug
Comment 2 Philip Withnall 2015-06-26 13:44:44 UTC
Migrated to Phabricator: http://phabricator.freedesktop.org/T96


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.