2012/6/15 José Luis Millán <[email protected]>: > 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.
Good point. So then... yes, 2012, Outbound / GRUU / Path, but a SIP dialog must be abruptly terminated if one of the peer behind NAT is TCP disconnected for 1 nanosecond. Great. -- Iñaki Baz Castillo <[email protected]> _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
