If there are any client transactions in existence, the client
transport uses the matching procedures of Section 17.1.3 to attempt
to match the response to an existing transaction. If there is a
match, the response MUST be passed to that transaction. Otherwise,
the response MUST be passed to the core (whether it be stateless
proxy, stateful proxy, or UA) for further processing. Handling of
these "stray" responses is dependent on the core (a proxy will
forward them, while a UA will discard, for example).
Robert Sparks wrote:
Do any of you know off the top of your head if and where 3261 specifies what an endpoint does with a non-INVITE response it receives for which it has no matching client transaction?We all know it ignores it, but I need to point at where we actually say that, and am not finding it quickly. I'm hoping one of you can short-circuit my search. Thanks! RjS _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
_______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
