#75 Contact/Via get a wrong address out of multiple candidates

[Mikhail Zabaluev]

Originally filed as Telepathy-SofiaSIP bug [ 1749217 ]:
http://sourceforge.net/tracker/index.php?func=detail&aid=1749217&group_id=191149&atid=936212

When there is an IPv4 network interface and also an IPv6 network interface up simultaneously, Sofia-SIP may choose to contact the proxy over IPv4, but supply the IPv6 address in the Contact URI.

Observed with NUTAG_PROXY tag (incl. set to refer to an IPv4 host explicitly).

[Mikhail Zabaluev]

Output of telepathy-sofiasip including Sofia-SIP debug output

[Mikhail Zabaluev]

Logged In: YES
user_id=313104
Originator: YES

Seems to be a common problem when multiple network interfaces are up (e.g. VPN, see https://bugs.maemo.org/show_bug.cgi?id=1860\).
More investigation is to follow.

[Mikhail Zabaluev]

Logged In: YES
user_id=313104
Originator: YES

In addition to assigning a default, and probably incorrect, Via header to every primary transport in agent_init_via() at nta/nta.c, it could be better to discover the proper local address (doable, with a race condition, on Linux using rtnetlink) for a secondary transport and use it for Via and Contact.