Re: [sr-dev] git:alexh/master: core modules/tm modules/sl: Make adding path and flags to redirected contacts optional

On Monday 08 August 2011, Klaus Darilion wrote: A registrar receives an invite from the proxy with the aor in the ruri. The registrar replies with a 302 with all the registered contacts for that aor. This is already possible ofcourse, but this set of patches enhance the Contact with a Route header containing the Path vector (if present) and a header parameter with the branch flags. Now the proxy can honor the Path by routing using the added Route header and for example NAT support can be done because the proxy now had the branch flags of each contact. Example: hosta: bflags: 2 Path: sip:192.168.1.2:5060;lr;received="sip:192.168.1.18:2048;transport;udp";nat hostb: bflags: 2 Path: sip:192.168.1.2:5060;lr;received;"sip:192.168.1.18:1144;transport;udp";nat Results in the following contact header in the 302: Contact: <sip:hosta@172.28.4.223:2048;line=b5psbzj0?Route=sip:192.168.1.2:5060%3blr%3breceived%3d%22sip:192.168.1.18:2048%3btransport%3dudp%22%3bnat>;q=0.3;flags=2, <sip:hostb@172.28.4.40:2048?Route=sip:192.168.1.2:5060%3blr%3breceived%3d%22sip:192.168.1.18:1144%3btransport%3dudp%22%3bnat>;q=0;flags=2. -- Greetings, Alex Hermann