2012/6/14 Olle E. Johansson <[email protected]>: > I think this is mentioned: > Section 5.3.2 > > Implementation note: Specific procedures at the edge proxy to > ensure that mid-dialog requests are routed over an existing flow > are not part of this specification. However, an approach such as > having the edge proxy add a Record-Route header with a flow token > is one way to ensure that mid-dialog requests are routed over the > correct flow. > > > Do we need a specification of this or is a solution just assumed?
Hi Olle, the issue I talk about is not in the outbound proxy but in the registrar. For GRUU stuff to properly work, the registrar must be a proxy in the route set of the dialog and, when an in-dialog request has a GRUU URI in the RURI and arrives to the registrar, it must "resolve" the RURI and replace it with the corresponding binding in the location database, this is: - Alice sends an INVITE with her public GRUU as Contact URI. - Later Alice's registrar receives an in-dialog request from Bob, so the request has Alice's public GRUU as RURI. - The registrar MUST replace the RURI with the corresponding binding of Alice. This is: the request MUST arrive to Alice without her GRUU in the RURI. The issue I exposed in my mail occurs because the proxy/registrar in which I'm testing GRUU does not replace the RURI of the in-dialog request when it contains a GRUU, so it's a bug in the proxy/registrar (K.........). Regards. -- Iñaki Baz Castillo <[email protected]> _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
