# 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
On 27/06/13 12:09, Tzafrir Cohen wrote: > On Thu, Jun 27, 2013 at 11:28:13AM +0100, Simon McVittie wrote: >> 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? > > It's in our LAN. To be completely specific: host.domain.name resolves to an IP address somewhere in 192.168.0.199/22? >> What's the domain part of your SIP URI? > > I wrote the account as '[email protected]' , which was good enough. And just to rule out weirdness: there is no _sip._udp.host.domain.name SRV record? >> 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.) Please do check these: they are significant. You can anonymize the 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". >> 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 > > This one did the trick. None of the other options seems to have > helped. That option is a workaround: on your particular network, it seems that 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 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
