Hi, RFC 5627 states (at least that is what I understand) that for mid-dialog requests in the authoritative proxy, the Path headers in the contact binding must be discarded:
6.1 +++ Special considerations apply to the processing of any Path headers stored in the registration (see RFC 3327 [3]). If the received request has Route header field values beyond the one pointing to the authoritative proxy itself (this will happen when the request is a mid-dialog request), the Path URI MUST be discarded. This is permitted by RFC 3327 [3] as a matter of local policy; usage of GRUUs will require this policy in order to avoid call spirals and likely call failures. +++ Meaning that the route set learned on dialog creation will mark, for ever, the path for mid-dialog requests. This would produce what Iñaki said in case one or both endpoints restart. The dialog route-set will point to a closed Outbound identifier and the Outbound proxy will respond with a 430 FLOW FAILED. Please, correct me if I misunderstood something, Thanks 2012/6/15 Iñaki Baz Castillo <[email protected]>: > 2012/6/15 Iñaki Baz Castillo <[email protected]>: >> 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.........). > > Sorry, I didn't read the corresponding thread in the proxy maillist, > in which it's explained how to accomplish this requirement :) > > -- > Iñaki Baz Castillo > <[email protected]> > > _______________________________________________ > Sip-implementors mailing list > [email protected] > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
