Scott Lawrence wrote:
> I think this can only happen if you're talking to something that's
> broken - either a UA that sends more than one final response to the same
> request, or a proxy that is returning more than one to you (it is
> correct for a proxy to return multiple 2xx responses, but anything >=
> 300 should be cause the proxy to just choose one).
It could be a proxy that isn't "broken", but which happened to crash and
restart, losing all its transaction state. Then if it receives final
responses from other forks, and has no matching transaction, it will
just forward the response statelessly.
Paul
> In any event, it seems to me that the simplest thing to do is to just
> construct an ACK that matches the new response and send it (otherwise
> the broken thing downstream may keep resending it).
>
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
