[Asterisk-Dev] BOUNTY $500 to solve bug/feature 2358 and produce code to us

[Tilghman Lesher]

On Thursday 02 September 2004 14:29, Arkadi Shishlov wrote:
> Actually, if you are satisfied with INVITE response packet content
> but not with the source address inside the IP packet, then it is quite
> easy to fix with Linux policy routing facilities. Just tell it to use
> 10.1.202.1 when it speaks to 10.1.202.0/24. lartc.org howto and iproute2
> package should help with this. If you need exact commands, let me know.
> Or I'm missing something?

The problem is that the SIP protocol violates network layer separation by
encoding IP layer information at the application layer.  Hence, SIP is
designed to ignore how information was transmitted to it and only to reply
to the address as stored in the application layer.  So the application itself
selects the IP used inside the packet, and the Linux routing policy is
completely ignored when choosing that address.  Currently, the address
is chosen solely based upon the routing table rules.  Once it has the route
that matches its destination, it looks up the address information for the
corresponding interface.

-- 
Tilghman