The Cambridge Collabora office has IPv6 connectivity via SixXS. In this situation, telepathy-sofiasip appears to prefer its IPv6 address (it appears in the nta::contact parameter). Some SIP servers can't cope with this, and will bounce incoming calls to voicemail if the intended recipient of the call registered in this way. Incoming calls to an N900 on the same WLAN and using the same account details work fine, because the N900 doesn't have the ipv6 module. A hackish workaround is to listen on IPv4 only: http://git.collabora.co.uk/?p=user/smcv/telepathy-sofiasip-smcv.git;a=shortlog;h=refs/heads/ipv4 Sjoerd suggests that a better version would be to prefer whatever protocol we're using to communicate with the server. (It's also possible that this is related to Debian switching on net.ipv6.bindv6only by default recently.)
Yes. This should be there until Sofia-SIP is patched to use protocol- (and perhaps route-) correct addresses in its message headers. Cf. https://sourceforge.net/tracker/?func=detail&aid=2007672&group_id=143636&atid=756076
Thanks, fixed in git master (feel free to cherry-pick it into 0.6.x if you want). I've cloned this bug to represent the damage done by this workaround.
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.