On Tue, May 10, 2011 at 12:33 PM, Iñaki Baz Castillo <[email protected]> wrote:
> Hi, a proxy does parallel forking for an INVITE to leg A and B.
>
> Later legA replies 480 so the proxy client transaction transitions to
> "completed" state and remains there for a while (a timer and so).
>
>
Hi Inaki, shouldn't when forking, proxy wait for all the replies and then
choose the best response to forward. From the Section 16.7 Response
Processing:
4. Add response to context
Final responses received are stored in the response context
until a final response is generated on the server transaction
associated with this context. The response may be a candidate
for the best final response to be returned on that server
transaction. Information from this response may be needed in
forming the best response, even if this response is not chosen.
Tells me that you have to wait for all forked destinations to answer?
Regards,
Brez
> A few seconds later, leg B (which has not received or processed the
> CANCEL yet) replies 200. What should do the proxy? forward the
> request? or ignore it? I assume it must forward it without changing
> the client transaction to "accepted" state (RFC 6026) as it was
> already in "completed" state. If not, leg B will not receive and ACK
> for the 200 (the UAC would be responsible o sending such ACK followed
> by a BYE).
>
> Thanks a lot.
>
> --
> 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
