#714253 telepathy-rakia: can bind to the wrong network interface

Package:
telepathy-rakia
Source:
telepathy-rakia
Description:
SIP connection manager for the Telepathy framework
Submitter:
Tzafrir Cohen
Date:
2026-11-12 18:53:09 UTC
Severity:
minor
#714253#5
Date:
2013-06-27 09:41:57 UTC
From:
To:
Dear Maintainer,

I'm trying to use empathy on Wheezy as a SIP client.

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

I would have expected the traffic to go through br0.

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

$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master br0 state UP qlen 1000
    link/ether d4:be:d9:64:77:94 brd ff:ff:ff:ff:ff:ff
5: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc mq state DOWN qlen 1000
    link/ether 60:67:20:51:83:28 brd ff:ff:ff:ff:ff:ff
761: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 100
    link/none
    inet 10.2.0.14 peer 10.2.0.13/32 scope global tun0
763: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
    link/ether d4:be:d9:64:77:94 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.199/20 brd 192.168.15.255 scope global br0
    inet6 fe80::d6be:d9ff:fe64:7794/64 scope link
       valid_lft forever preferred_lft forever

#714253#10
Date:
2013-06-27 10:28:13 UTC
From:
To:
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.

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@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.)
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

#714253#15
Date:
2013-06-27 11:09:53 UTC
From:
To:
Hi,

Thanks for your prompt reply,

Right.

It's in our LAN.

I wrote the account as 'user@host.domain.name' , which was good enough.

None were set (except proxy-host, which I tried to set manually and
later relaised was unnecessary).

This one did the trick. None of the other options seems to have helped.

#714253#20
Date:
2013-06-27 11:47:22 UTC
From:
To:
# see below for explanation
clone 714253 -1
reassign 714253 telepathy-rakia
retitle 714253 telepathy-rakia: can bind to the wrong network interface
retitle -1 empathy: no UI for tp-rakia's local-ip-address parameter
severity -1 wishlist
close -1 3.8.3-1
thanks
somewhere in 192.168.0.199/22?
SRV record?
results if you must, as long as they're the same "shape" in terms of
things like "default route is via a gateway on the x.y.z.w network".
telepathy-rakia (or perhaps Sofia SIP, the library it uses) doesn't
automatically choose the right source address. I'm reassigning your
original bug to telepathy-rakia to represent that.

Empathy 3.8 in experimental does have "advanced" UI for the
local-ip-address and local-port parameters, but 3.4 in stable/unstable
doesn't. I'm using the cloned wishlist bug to represent that.

    S

#714253#33
Date:
2026-11-12 18:52:56 UTC
From:
To:
Dear submitter,

as the package telepathy-rakia has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1118550

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)