Dean Willis wrote:
Here's a question:
A UA has registered two flows to one instance. It has one gruu. The UA
uses the gruu as the contact in a dialog-forming request.
An in-dialog request (for example, BYE) is sent back to the UA. On
which flow does it get routed?
From gruu-15:
If there are no registered contacts bound to the GRUU, the server
MUST return a 480 (Temporarily Unavailable) response. If there are
more than one, there are two cases:
1. The client is using draft-ietf-sip-outbound [13] and registering
multiple contacts for redundancy. In that case, these contacts
contain reg-id Contact header field parameters, and the rules
described in Section 7 of draft-ietf-sip-outbound [13] for
selecting a single registered contact apply.
2. The client was not using SIP outbound, in which case there would
only be multiple contacts with the same instance ID if the client
had rebooted, restarted and re-registered. In this case, these
contacts would not contain the reg-id Contact header field
parameter. The proxy MUST select the most recently refreshed
contact. As with draft-ietf-sip-outbound, if a request to this
target fails with a 408 (Request Timeout) or 430 (Flow Failed)
response, the proxy SHOULD retry with the next most recently
refreshed contact. Furthermore, if the request fails with any
other response, the proxy MUST NOT retry on any other contacts
for this instance.
I believe: It gets routed on the flow that formed the dialog, as long as
that flow exists. The proxy has stored dialog state and knows which flow
the dialog-forming request used.
The GRUU spec assumes one contact per gruu. Outbound transforms this to
multiple contacts and multiple flows per gruu. I think this requires
further specification as to flow selection, possibly for out-of-dialog
messages and almost definitely for in-dialog messages. Perhaps this is
documented somewhere and I've just missed it.
Any clues?
--
Dean
_______________________________________________
Sip mailing list https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [EMAIL PROTECTED] for questions on current sip
Use [EMAIL PROTECTED] for new developments on the application of sip
_______________________________________________
Sip mailing list https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [EMAIL PROTECTED] for questions on current sip
Use [EMAIL PROTECTED] for new developments on the application of sip
