[Pkg-telepathy-maintainers] Bug#714253: empathy: no way to control the network interface it binds to

Simon McVittie smcv at debian.org
Thu Jun 27 10:28:13 UTC 2013


On 27/06/13 10:41, Tzafrir Cohen wrote:
> I'm trying to use empathy on Wheezy as a SIP client.

Empathy doesn't actually implement SIP (or any other IM protocol) so
this might actually be a telepathy-rakia bug, but I won't reassign it
right now, since it's possible that Rakia can do what you want but
Empathy lacks UI for it.

> I have a tunnel (tun0) set up to a remote interface, as well as eth0
> bridged through interface br0.

Am I right in thinking the bridge is trivial (only contains one real
interface, eth0)?

What is the IP address of the SIP server? Is it on the other side of the
tunnel, or on the bridged network, or somewhere else?

What's the domain part of your SIP URI? If it's something at example.com,
what do you get from "host -t SRV _sip._udp.example.com", and if there's
a SRV record, what's the IP address of the hostname listed there?

What routes do you have? ("ip route ls".) What route does the kernel
think it should take to the SIP server? ("ip route get 1.2.3.4" or
whatever.)

> I tried to configure a SIP account on a local SIP server. This, however,
> has completely failed, as empathy tried to connect through tun0.

If I remember correctly, telepathy-rakia and the sofiasip library it
uses do have some odd binding-to-interfaces behaviour, which is
apparently important for some uses of SIP.

If you list accounts with "mc-tool list" then inspect your SIP account
with "mc-tool show sofiasip/sip/mangled_form_of_its_name" (you'll
hopefully see what I mean when you look at the "mc-tool list" output),
does it have any of these parameters set: registrar, proxy-host,
transport, loose-routing, discover-binding, local-ip-address,
local-port? If so, what are their values?

It's possible that setting local-ip-address might do what you want:

    mc-tool update sofiasip/sip/mangled_form_of_its_name \
        string:local-ip-address=192.168.0.199

but if that works, please reply to this bug and say so - ideally it
would never be necessary.

A debug log from telepathy-rakia would be useful information to have:
please see <https://wiki.gnome.org/Empathy/Debugging> for details.

If you need to debug "the old way" to get logs from telepathy-rakia, the
most helpful environment variables to set are described in the
telepathy-rakia man page (RAKIA_DEBUG=all, RAKIA_PERSIST=1, TPORT_LOG=1
and optionally RAKIA_LOGFILE).

    S



More information about the Pkg-telepathy-maintainers mailing list