2012/6/14 Iñaki Baz Castillo <[email protected]>:
> *** ISSUE: ***
>
> - If alice sends an in-dialog request to bob (i.e. re-INVITE) OB-1
> won't change the INVITE route set (of course) so the Outbound
> identifier of alice's connection will still identifying the
> *PREVIOUS* alice's connection.
>
> - So later bob sends a new in-dialog request to alice (i.e. BYE). When
> the request arrives to OB-1, that proxy will realize that the Outbound
> identifier belongs to an already closed connection so will reply 430
> "Flow Failed" to PROXY/REGISTRAR. And PROXY/REGISTRAR cannot perform
> "serial forking" since it's just an in-dialog request and therefore it
> SHOULD NOT examine the Request URI (which contains the public GRUU of
> alice).
Ok, by re-reading RFC 5626 it seems that the proxy receiving an
in-dialog request whose Request URI contains a GRUU URI should route
based on the Request URI instead of Route headers, am I right?:
6.1. Request Targeting
If the Request-URI contains the "gr" URI parameter and is equivalent,
based on URI comparison, to a GRUU which is currently valid within
the domain, processing proceeds as it would for any other URI present
in the location service, as defined in Section 16.5 of RFC 3261 [1],
except that the "gr" URI parameter is not removed as part of the
canonicalization process. This is the case for both out-of-dialog
requests targeted to the GRUU, and mid-dialog requests targeted to
the GRUU (in which case the incoming request would have a Route
header field value containing the URI that the proxy used for record-
routing.).
--
Iñaki Baz Castillo
<[email protected]>
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
