>>As I described I do know that my proxy always behaves as a stateful proxy so >>forwarding a CANCEL for which
I understand what you are saying - your proxy is stateless. But my understanding was that it should statelessly forward EVEN IF it's stateful proxy. >>Then, why should it forward an unknown CANCEL? I thought the purpose was that if something goes wrong and no context is found - then you have to make a best effort to forward it somewhere. But maybe I'm wrong about that. -----Original Message----- From: Iñaki Baz Castillo [mailto:[email protected]] Sent: 19 April 2011 14:19 To: Attila Sipos Cc: [email protected] Subject: Re: [Sip-implementors] Stateful proxy and CANCEL for a non matchingtransaction => 481? 2011/4/19 Attila Sipos <[email protected]>: > It is saying you MUST forward it. > You forward it (without creating state) to the endpoint to which you would've > forwarded a similar INVITE. Hi Attila. As I described I do know that my proxy always behaves as a stateful proxy so forwarding a CANCEL for which there is not a server transaction will just never work in my scenario. RFC 3261 states: If a response context is not found, the element does not have any knowledge of the request to apply the CANCEL to. It MUST statelessly forward the CANCEL request (it may have statelessly forwarded the associated request previously). But this cannot be my case as my proxy neves forwards statelessly an INVITE. Then, why should it forward and unknown CANCEL? I will not do it as it's 100% useless. My question is: can the proxy reply a 481 by its own in this case? Thanks a lot. -- Iñaki Baz Castillo <[email protected]> _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
