Hi, "9.2 Server Behaviour" doesn't clarify the UAS behaviour very well:
1) UAS receives a CANCEL for which there is not an INVITE transaction. UAS
must reply a 481 but:
- Should UAS generate a transaction for that CANCEL?
2) - UAS receives a CANCEL for an INVITE transaction for which UAS has already
sent a final response. In this case RFC3261 says:
"the CANCEL
request has no effect on the processing of the original request, no
effect on any session state, and no effect on the responses generated
for the original request."
- But should UAS reply a 4XX?
- In that case, should it create a transaction? I hope no, since a maliciosus
user could generate many CANCEL's and the UAS will create so many
transactions.
3) UAS receives a CANCEL that matches an active NON-INVITE transaction. RFC
says:
"A CANCEL request has no impact on the processing of
transactions with any other method defined in this specification
(INVITE)".
- Which response should UAS sent? a 481? a 400?
- Should it create a transaction for this?
I assume reply for 3) are "481" and "No", and probably this never occurs since
non INVITE transactions are expected to finish inmediatelly.
Thanks for clarification.
--
Iñaki Baz Castillo
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
