> > 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? >
IMHO. The mandatory requirement imposed sounds a bit insane really. I would say policy like this should be left for operations/deployment decisions. I can't see this to work, for example, in IMS world. It is confusing really. If there's a document correcting this ruling, I would love to see somebody to bring it to our attention here. Thank you, Regards, _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
