For completeness... 

RFC 6026 updates RFC 3261 concerning proxy behavior when receiving responses 
for unknown requests.  The following is from section 4 summary: "It also 
forbids forwarding stray responses to INVITE requests (not just 2xx responses), 
which RFC 3261 requires."

> -----Original Message-----
> From: [email protected] [mailto:sip-
> [email protected]] On Behalf Of Iñaki Baz
> Castillo
> Sent: Friday, June 10, 2011 8:47 AM
> To: Bob Penfield
> Cc: [email protected]
> Subject: Re: [Sip-implementors] About CANCEL in a proxy (no changes to
> server/client transaction)
> 
> 2011/6/10 Bob Penfield <[email protected]>:
> > Except for 100 (Trying), a 1xx should always be forwarded upstream
> toward the UAC. Remember, all transactions complete independently.
> There may be a 2xx final response right behind the 1xx response. The
> CANCEL can only change the state of an INVITE transaction in the UAS.
> 
> Yes, exactly what I had in mind :)
> I just wonder how useful is relaying a 1XX response upstream in case
> the proxy has sent a CANCEL upon the arrival of such response.
> 
> But anyhow it's fully clear. Thanks a lot.


_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors

Reply via email to