[sr-dev] Using GRUU and outbound

[José Luis Millán]

Hi all,


2013/5/2 Olle E. Johansson <oej at edvina.net>

>
> 30 apr 2013 kl. 20:16 skrev Juha Heinanen <jh at tutpro.com>:
>
> > Peter Dunkley writes:
> >
> >> If you look at the recent (yesterday and today) discussion on DISPATCH
> >> the conclusion appears to be that this is how it should work and that
> >> RFC 5626 should have been clearer on the behaviour.
> >
> > i read the discussion and don't understand why would route set change.
> > if ua looses connection to its proxy, it sets up a new one, but the
> > proxy (which is in the route set established by r-r headers) is still
> > the same.
>
> If you are using edge proxys separate from the registrar, the new
> registration may come through another edge proxy, so the
> gruu will resolve in a new path to the client, which replaces
> the existing route through the possibly dead edge proxy.
>

Such new path to the client will be used instead of the old and invalid one
as far as I understand from RFC 5626, chapter 7:

```

The proxy uses the next-hop target of the message and the value of
   any stored Path header field vector in the registration binding to
   decide how to forward and populate the Route header in the request.
   If the proxy is co-located with the registrar and stored information
   about the flow to the UA that created the binding, then the proxy
   MUST send the request over the same 'logical flow' saved with the
   binding, since that flow is known to deliver data to the specific
   target UA instance's network flow that was saved with the binding.


```

Which means that a newly created registration binding (following the
procedures defined in chapter 4.4) will contain the PATH route with the new
and valid flow token, and such 'logical flow' MUST be used instead of that
in the Route. Hence, the Route header(s) pointing to the old and deprecated
'logical flow' is replaced with the new one gathered from the registration
after the flow failure.


>
> /O
>
> _______________________________________________
> sr-dev mailing list
> sr-dev at lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
>



-- 
José Luis Millán
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-dev/attachments/20130502/fc2cd6f3/attachment-0001.html>