Hi, > -----Original Message----- > From: ext Inca Rose [mailto:incar...@gmail.com] > Sent: Friday, January 21, 2011 3:50 PM > To: Pekka Pessi > Cc: sofia-sip-devel@lists.sourceforge.net > Subject: Re: [Sofia-sip-devel] Multi home and sofia-sip > > Also there is no way to check from which NIC the proxy is reachable, > imagine a VPN situation where the proxy is only > reachable from the VPN but not from the real NIC.
This is not fully solvable on Linux, I believe. You can read the routing table, but it can change between the moment you read it and the moment you try to send a message. I think a practical approach is to see which interface has the default gateway route, and treat it as the source interface for purposes of Via/Contact/etc. This will cover the majority of UA cases with VPN and otherwise. The change detection is still needed, though, at least after transport timeouts or transactions timing out with no responses. In fact, the IP binding announced in headers should not matter for modern day proxies, as long as they use symmetric response routing as indicated by the UA, and the UA updates the registration contact based on the reflected address. Unfortunately, in some cases the proxies are too picky. -- Mikhail ------------------------------------------------------------------------------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d _______________________________________________ Sofia-sip-devel mailing list Sofia-sip-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel